Docs/Features and where to use them

Features and where to use them

A practical map from what you want to do to the relevant ACC workspace.

Implementation checked against deployed revision · account enablement varies13 October 2026

Plan and coordinate

Workspace: discuss a plan with a manager agent, revise scope and coordinate tasks. Inbox: respond to decisions and work that needs your attention.

Build and review

Work: boards, tables and task structure. Agents: agents, runners, models and templates. Delivery: PRs, previews/deploys, contracts, ownership and relevant graphs.

Keep context and understand progress

Knowledge: the available project knowledge surfaces. Insights: progress, cost and reliability views where enabled. Recorded decisions help subsequent work find useful context; review remains necessary.

People and administration

Team: collaboration and membership. Admin: organization configuration and controls allowed by your role. Your account settings manage your own identity and sessions.

Supported tools are not identical

Claude Code is the default batch engine. Claude Code and Codex have registered chat adapters. Codex and Gemini batch execution require runner enablement; Gemini chat is currently retired in the reviewed implementation. Integrations have different authentication and execution requirements. Check the selected engine and configuration before assigning work. FlowGraph is a separate GetSet tool; follow the current integration status.

Need something else?

Request a feature or report a problem. Requests help prioritize the roadmap; availability and delivery dates are confirmed separately.

Use tools installed on the execution machine

Agents can use command-line tools available through the connected machine’s terminal, alongside the supported execution engines. Build, test and deployment commands are examples; the named provider connections are not an exhaustive list of your possible CLI workflow. Each tool must be installed, authenticated and accessible with the required permissions. Execution depends on the chosen engine and machine environment. This does not mean every tool has a dedicated ACC interface or identical capabilities.

Broader direct tool integrations in ACC are planned for phase 2. No delivery date is promised. See the product status for current limitations.