shipper_unblock
shipper_unblock
Section titled “shipper_unblock”Attempt to unblock a blocked issue (shipper:blocked label). Runs the unblock prompt to check if the blocker is resolved. Headless mode.
When to use
Section titled “When to use”Use this when an issue is marked shipper:blocked and an agent needs to determine whether the blocker has cleared and the workflow can continue.
Behavior hints
Section titled “Behavior hints”- idempotentHint: true — Retrying the same call is expected to be safe once the target state is reached.
- openWorldHint: true — The tool reaches GitHub or other external systems outside the MCP server.
Input schema
Section titled “Input schema”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| issue | integer | yes | - | GitHub issue number. |
Example call
Section titled “Example call”{ "issue": 42}Example result
Section titled “Example result”Verdict: unblockedReason: The dependency has merged and the blocked work can continue.
---Blocker resolved.
Session log: /tmp/shipper/session.logError modes
Section titled “Error modes”- Missing unblock verdict: Unable to recover the unblock verdict from post-run metadata.
- Timed out worker: [timed out] shipper unblock
—mode headless - Failed worker: [exit
] shipper unblock—mode headless - GitHub, session, or result-file failure: GitHub, session, or result-file failure:
Related tools
Section titled “Related tools”