Start your first app in Agent Control Panel
Create a project, describe a goal, review the plan, and follow the work on ACP's board.
Begin with a concrete outcome
Sign in, open your apps dashboard, and start a new project or select an existing one. The Mission conversation is where you describe what you want built. A useful first goal names the user, the behavior, and the evidence you would accept: for example, a small task tracker where a user can add a task, mark it complete, and see that state after a refresh.
You do not need to translate the goal into implementation tickets yourself. ACP's planner asks follow-up questions when details would change the result. Answer those questions, inspect the resulting plan, and approve it before expecting the build to advance. For interface work, Design may begin while the planner finishes UI tickets; the board remains the place to watch the accepted work.
- State what should work for a person using the app, not only which framework to use.
- Mention a repository or existing app when you want a change rather than a new project.
- Decide how you will check success: a visible flow, a test, or a reviewed change.
Follow the board, then inspect the result
After approval, the board shows tickets and their progress. A ticket can move through building, testing, and review; a failed check can send it back for another pass. Open a ticket to read its output and evidence instead of treating an agent's final message as proof that the feature is done.
The delivery route depends on how you started. New Plan → Feature uses a shared feature branch and one pull request for its tickets when GitHub publication is configured. A Talk, Build, or Change flow can instead land on the project's main branch. Check the branch and result shown for your run before assuming a pull request will appear.
Start small and keep ownership
For a first run, prefer one user journey over a complete product roadmap. You can inspect the plan, ask for a change, or stop and revisit the goal. Keep your own review of behavior, data, and repository changes in the loop; the pipeline supplies evidence, but it cannot decide your product requirements for you.