missions

Send a follow-up instruction to a mission

The API equivalent of commenting on the tracker issue, for callers with no tracker identity to post under. An instruction sent this way reaches the agents exactly as a comment would, and carries the same priority over the automated guards that would otherwise hold a stuck mission. A follow_up additionally puts the builder back on the mission's open pull request, overriding the review and QA verdicts already recorded: without that, re-triggering a mission whose pull request is already approved correctly concludes there is nothing to do. Returns a receipt naming what was recorded and what it will cause, so a caller never has to guess whether delivery succeeded.

post/missions/{issueId}/instructions

Request

  • Base URL: https://api.letsship.ai/v1
  • URL: https://api.letsship.ai/v1/missions/{issueId}/instructions
  • Auth: none declared

Path parameters

issueIdstring required

Headers

idempotency-keystring

Retrying a request with the same key charges it once and starts (or delivers) it once. Use a new key for new work.

Example:7f9c2ba4-e88f-11ee-9a1a-0242ac120002

Request body

bodystring required

What the agents should do. Travels verbatim into the builder's prompt.

kind'follow_up' | 'note'

follow_up asks for a change and dispatches the builder against the mission's open PR, overriding cached review/QA verdicts. note records context for whatever runs next and dispatches nothing. Stated explicitly rather than inferred, so the outcome never depends on how the platform reads intent.

Example request

{
  "body": "Keep the current Node compatibility - override nopt rather than narrowing the supported range."
}

Response

Instruction recorded. dispatch says what it will cause.

instructionIdstring required

Id this instruction was recorded under. Deduplicates a retried request.

issueIdstring required
recordedtrue required

The instruction is durably in the mission's inbox. Always true on a 200.

missionActivitystring nullable required

The mission's activity at the moment the instruction landed.

Example response

{
  "instructionId": "ins_9b8e2a3f3c4d",
  "issueId": "GH-1280",
  "missionActivity": "ready_to_merge",
  "dispatch": {
    "willDispatch": true,
    "role": "builder"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.