Resume
cmd/crewship/cmd_resume.go continues a previous session by threading --chat <id> into the standard run flow against the agent that owns the chat. Four resolution paths:
If the agent slug isn’t part of the resolved object, the chat detail is fetched from
GET /api/v1/agents/{agentId}/chats/{chatId} to recover it.
crewship resume [chat-id | run-id | pr-url]
No flags of its own — all flags belong to crewship run (it’s the dispatch target). The two flags that get forced are --chat <id> and --interactive=true.
Examples
Common errors
interactive picker requires a TTY; pass a chat-id or run-id— running without a TTY but no argument.run <id> has no associated chat to resume— the run pre-dates chat threading or was created without one.could not determine agent for chat <id>— chat detail lookup did not surface an agent.no recent sessions to resume— the workspace has no CLI-origin chats in the last 10 entries.no session found for PR <owner/repo#n> — pass a chat-id directly— journal search came up empty; fall back to the chat-id form.list recent: chats endpoint: <err>; fallback runs: <err>— both/api/v1/chatsand the/runsfallback failed; both errors are surfaced to make the actual problem identifiable.
See also
crewship history— list of recent runs, grab a chat-id from the table.crewship recap <chat-id>— summarise the session instead of continuing it.crewship retry <run-id>— start a fresh run with the same prompt.