You set the mission. Agents ship it.

Drop a goal. ACP turns it into a plan and puts agents on the floor — building, testing, and reviewing while you watch.

From goal to delivery
  • Plan
  • Build
  • Test
  • Review
PIPELINE
3
core build, test, and review stages
FEATURE
1
shared pull request per Feature
PROJECTS
1
shared board per project
FREE SOLO
0
personal API keys required
The floor

An office that never closes.

These illustrated cards show roles across the workflow, from planning to delivery. Your signed-in board shows actual runs and their current states.

agentcontrolpanel.devWorkflow illustration
PlannerWorkflow role
Running
Turn your idea into a plan
Agree on scopeExample
BuilderWorkflow role
Running
Build the agreed change
Follow the planExample
TesterWorkflow role
Testing
Check the result
Check requirementsExample
ReviewerWorkflow role
Review
Review the change
Find issuesExample
UnblockerWorkflow role
Ready
Help when work gets stuck
Rescue when neededExample
DeliveryWorkflow role
Ready
Prepare the result
Follow delivery gatesExample
How work movesDEMO
infoDiscuss your idea and agree on the scope
infoTurn the agreed plan into ordered tasks
infoBuild the next task in the Feature
infoTest the change against its requirements
info
The pipeline

Build, test, review, and deliver.

The workflow tracks each stage and can route blocked work to an unblocker. The path depends on the ticket and project.

RunningAgent works on the ticket.
The loop

Four beats, end to end.

  1. Describe it

    One sentence is enough. The planner writes a real spec with acceptance criteria and a dependency order.

  2. Tested & reviewed

    A tester checks the result, then a separate reviewer reads the diff. Failed stages send the ticket back for more work.

  3. Deliver the change

    A Feature uses one shared pull request. Other workflows may create a ticket PR or update the project directly.

For teams

Your crew and their agents, on one floor.

Owners invite teammates, assign tickets, and gate merges behind human review. Free Solo runs on the platform wallet — not each assignee's personal API keys or a live per-seat subscription.

SZRFRHRoles, per-app access, shared spend limits.
No API key required

A role for every stage.

  • PlanScope the work
  • BuildMake the change
  • TestCheck the result
  • ReviewInspect the change

Put an agent on it.

Free to plan. No card. Your repo stays yours.

Start building