Delegate work to a Capy agent
capy_delegateStart a cloud agent to complete engineering work independently, then monitor progress with status or block until done.
Instructions
Start a new Capy agent thread in the cloud to do a piece of engineering work. The agent runs in its own isolated VM with the project's repos checked out, and works independently of this conversation. Call this once per independent piece of work: calling it several times gives you several agents running genuinely in parallel.
Write the prompt the way you would brief a competent engineer who cannot ask you follow-up questions: state the goal, the acceptance criteria, and any constraint that is not obvious from the code.
Returns a thread id. Use capy_wait to block until the work is done, or capy_status to poll. Note that starting a thread consumes Capy credits.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Lowercase tags to attach, useful for grouping a batch of parallel delegations so you can find them later with capy_list (e.g. ["refactor-batch"]). | |
| model | No | Model for the Captain (planner) agent. Omit to use the project default. List available models with capy_models. | |
| repos | No | Override which repos and branches the agent starts from. | |
| speed | No | Captain speed setting. | |
| prompt | Yes | What the agent should do. Be specific about goal and acceptance criteria. | |
| reasoning | No | Captain reasoning effort. | |
| project_id | No | Capy project id. Defaults to CAPY_PROJECT_ID. List them with capy_projects. | |
| build_model | No | Model for the build (executor) agent, if it should differ from the Captain. | |
| build_speed | No | Build agent speed setting. | |
| slack_channel | No | Mirror the thread into this Slack channel, if Slack is connected. | |
| build_reasoning | No | Build agent reasoning effort. |