rooster

Respond To Issue Intake

Dumb persist of Rooster's turn. Calls NO model.

trace_steps are shown to the reporter as what Rooster actually did while they talked, so they must be real tool calls, never illustrative ones. A turn with no draft is a question, which is the normal first turn.

Passes Rooster's own Slack notifier (_slack_notifier, below -- NOT Damien's bot, see that function's own incident writeup) so issues_intake.respond can DM the reporter that this turn landed. Same seam every other Rooster-lifecycle DM in this file already goes through (build-question, merged, build-failed, staged).

post/api/rooster/issues/intake/{conversation_id}/respond

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/rooster/issues/intake/{conversation_id}/respond
  • Auth: none declared

Path parameters

conversation_idstring uuid required

Request body

replystring required
trace_stepsstring[] nullable
draftobject nullable
agent_providerstring nullable
agent_modelstring nullable
claude_session_idstring nullable

Response

Successful Response

object required

Changes

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