Projects

Projects are the top-level workspace in ACP. They connect planning, execution, resources, schedules, and the agents that work on them.

Projects

Organize work, resources, tickets, and automation inside one ACP workspace.

What projects are

Projects define the operating boundary for a product or workflow in ACP. They collect threads, mission control runs, tickets, resources, schedules, and the agents assigned to the work so execution history stays attached to the system being built.

Use one project per app, system, customer workflow, or internal initiative.

Keep tickets, mission control output, and runtime resources in the same workspace.

Let teams work with one shared planning and execution context.

How projects structure work

ACP projects are designed for ongoing operational work, not just one-off prompting. Mission control can turn a brief into structured tasks, and those tasks can become real execution threads that work against persistent computers and resources.

Plan with mission control and convert results into executable tickets.

Assign tickets to agents and teams or start work manually.

Track project state across board, backlog, calendar, and thread history.

What belongs in a project

Resources that should move together usually belong in one project. That includes computers, web apps, functions, auth modules, databases, schedules, and the agents that maintain or extend them.

Attach computers, published resources, and schedules to the same project.

Keep deployment surfaces close to the work that creates them.

Use project scope to reduce context switching for both humans and agents.