What was checked on 13 October 2026
The ACC production deployment is marked ready and identifies source revision 60cc3321. This guide was checked against that revision and the retained documentation. A ready deployment establishes which code was published; it does not establish that every capability is enabled or tested for your account.
Available to evaluate in the beta
ACC provides an organisation-management and coordination workspace for individuals and teams: goals and planning, work hierarchy and boards, people and agent roles, decisions, reports, repositories and connected-machine execution. Digital product and service delivery is the first use case. Setup, permission and provider requirements still apply.
Limited or configuration-dependent
- Execution engines: Claude Code is the default batch engine. Claude Code and Codex have registered chat adapters. Codex and Gemini batch adapters require runner enablement. Gemini chat is currently retired in the reviewed implementation; do not assume identical features across tools.
- Merge lanes: lane routing and merge-train execution are separately controlled, default-off capabilities. Ask the administrator which are enabled. Checks, review holds and deployment verification remain necessary.
- People and authority: workspace membership and project permissions constrain access. Agent job roles are distinct from human administration roles.
- Execution and browser access: use the web workspace across devices. Work runs on a connected machine with the right repository and provider access; that machine must stay online.
- Data controls: personal exports, organisation-owned work and deletion have different coverage. ACC also stores coordination data. Read the data guide, export guide and deletion guide.
In development
FlowGraph integration: FlowGraph is a separate graph-memory tool. Integration with ACC is in progress; the final interface and installation approach may evolve. Onboarding, broader data controls and tool coverage continue to develop.
Planned and future vision
Broader direct tool integrations are planned for phase 2; wider connectors and MCP coverage remain a roadmap. Agents can use installed, authenticated and permitted CLI tools through a connected machine’s terminal today. That execution path is distinct from a dedicated integration in the ACC interface; capabilities depend on the engine and environment. Cross-provider commitments, a GetSet provider network or marketplace, and local or industrial service composition are future vision. No automatic physical fulfilment or established provider network is offered by this beta.
Some ACC interfaces and source paths support MCP and terminal operations. Their existence does not imply every proposed connector inside Claude, ChatGPT or Gemini—or general terminal mirroring—is available to every user. Confirm your setup with support.
Beta terms and uncertainty
Accepted applicants receive free ACC access. You provide AI subscriptions or API credits and cover VPS or hosting costs. Future ACC pricing is undecided. No fixed roadmap dates are promised. Legal pages remain labelled drafts; feature availability and user rights must be understood alongside the full data and policy explanations.