Run an armed project Agent
run_project_agentQueue real execution for an armed Agent on a project: provide task, model, and idempotency key. Server enforces saved limits and access before the job starts.
Instructions
Queue real execution for a project-linked Agent the person already test-ran and armed. The immutable saved Limits, project access, account fuse, and online Engine requirement are enforced server-side before a job exists.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>",
"agent_id": "<agent_id>",
"task": "<task>",
"model": "<model>",
"idempotency_key": "<idempotency_key>"
},
"name": "run_project_agent"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | Concrete task for this run. This cannot widen the Agent's saved tools, folders, network, send, change, or spend authority. | |
| model | Yes | CLI model available through the account's online Engine. | |
| agent_id | Yes | Already-armed 2ools Agent ID. | |
| project_id | Yes | Project this Agent is assigned to. | |
| idempotency_key | Yes | Caller-generated unique key. Reusing it returns the original run instead of starting another. |