Send a follow-up instruction to a mission
send_mission_instructionTell a mission what to change. Use kind='follow_up' (the default) to ask for a change: the instruction reaches the agents AND dispatches the builder against the mission's open pull request, overriding cached review and QA verdicts. Use kind='note' to record context for whatever runs next without starting any work. A restart is a different thing: it re-evaluates an unchanged pull request against its cached verdicts, and so changes nothing. Returns a receipt saying what was recorded and what it will cause. This tool calls the SHIP API, documented at https://letsship.ai/docs/api. Requires the missions:write token scope.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | What the agents should do. Travels verbatim into the prompt | |
| kind | No | follow_up (default) dispatches the builder; note records context and dispatches nothing | |
| issueId | Yes | Issue id the mission is tracked under, e.g. SHIP-244 or GH-1280 |