Sign in
latestOpenAPI 3.0.02026-08-12277306567.6 KB

fe2dff9fb04b

Ticket

Report external coding-agent progress

Called by the Gleap MCP report_progress tool. Updates the ticket's handoff state (live activity in the dashboard), appends to the progress trail, and registers pull-request links for resolve-on-merge. When the report carries a customerShipMessage, shipMessage.state in the response says what became of it (parked / armed_immediately / already_armed / already_replied / mode_none / guard_tripped / error / none_requested) — the MCP tool relays that to the agent so it never guesses whether an automatic follow-up exists.

post/tickets/{ticketId}/agent-progress

Path parameters

ticketIdstring required

Headers

projectstring required

Request body

phase'investigating' | 'reproduced' | 'fixing' | 'pr_opened' | 'blocked' | 'done' required
messagestring required

One-line status shown live in the dashboard (aim for ~10 words).

prUrlstring

Pull-request URL; registers the PR for resolve-on-merge.

agentNamestring

Reporting agent's product name (e.g. "Claude Code", "Codex").

sessionIdstring

Stable id for the agent's session, sent on every call — the upsert key that lets multiple agents work one ticket in parallel. Must match [A-Za-z0-9._-]{1,100}; anything else (and omitting it) falls back to agentName as the key.

customerShipMessagestring

Operator-approved customer "ship message" (plain text, max ~2000 chars), drafted while the agent still has full context. Gleap shows it on the ticket as a scheduled reply without a date and sends it automatically after the registered PR merges, per the project's post-merge timing settings; the ticket closes after delivery. Send it with pr_opened or done; the newest report replaces the draft.

Response

Ok

{"stackTrail":"paths:/tickets/{ticketId}/agent-progress:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}