Send message
Send a follow-up message to a task.
/plan to have the agent plan first, or /goal <objective> to set a goal it works toward across turns. To implement a proposed plan, send a message starting with /agent, as the app’s Implement button does (/agent Implement the plan I just approved.). files attaches assets, with each file’s content inlined as a data: URL (remote http(s): URLs are not fetched).
Omit userIntent to keep where the task runs: its own fork, or the main environment for a task created with "DEV_ENVIRONMENT" (Fork off in the app). Sending userIntent changes that for this and later runs. The legacy values "PLAN", "ASK", and "GOAL" are still accepted but treated as "SWE".
Omit agent and reasoningEffort to keep the task’s model and effort. agent can select another full provider/model ID of the task’s existing harness, and reasoningEffort changes its effort.
API keys reach cloud tasks only. Local project chats return 404; continue them in the Twill app.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Follow-up message or instructions.
1Omit to keep where the task runs. SWE moves it to its own fork and DEV_ENVIRONMENT to the main environment, for this and later runs. The legacy values PLAN, ASK, and GOAL are still accepted for backward compatibility and treated as SWE.
SWE, SCHEDULE, DEV_ENVIRONMENT Optional file attachments provided as UI message file parts.
API keys are cloud-only. Local project chats are started in Twill Desktop.
Complete provider/model ID within the task's existing harness.
Reasoning effort supported by the selected model.
low, medium, high, xhigh, max, ultra Response
Message accepted