Start and configure an agent
Start an agent in the right project with a clear request and a suitable configuration.
Last updated 16 September 2026
Start an agent in the right project with a clear request and a suitable configuration.
Before you start
Add the project first and make sure your coding provider is available. A new conversation uses the selected project; creating a chat alone does not create an isolated copy of its files.
The new-agent composer keeps the request and its configuration together. Confirm the selected project before sending.
Step by step
Select the project and open New Agent. Check the project name under the composer before writing the request.
Open the model control and choose the provider and model. Choose an available reasoning effort for the task; the options depend on the model.
Review the access control separately. Choose how much supervision the agent should need for file changes and other operations.
Write a concrete request: the expected behavior, relevant context, limits, and how the result should be checked. For example, ask for a clearer empty state and specify the action users should take when there are no updates.
Attach relevant files, docs, or images through the composer. Keep the request focused on the material the agent needs, and confirm that linked requirements belong to this project.
If you need an approach before implementation, focus the composer and press Shift+Tab to enable Plan. Check that the Plan chip is visible. Otherwise keep the default working mode.
Read the whole draft, then send it. Follow the resulting conversation, answer questions, and inspect the work before deciding it is complete.
What to expect
A new agent conversation starts with the selected project, configuration, and request. Its progress and results remain in that conversation.
Troubleshooting and useful details
If Choro asks you to choose a project or describe the task, complete that part of the draft before sending. Check provider availability when no model can be selected. For simultaneous implementation that must stay separate, consider Solo; two ordinary conversations can work in the same project folder.