Recall
cmd/crewship/cmd_recall.go hits the journal ?q= FTS5 endpoint and renders results in a snippet form optimised for question-answering (“how did we ship the auth fix?”). Different mental model from crewship journal, which is for filtered tailing/auditing — the two share the underlying endpoint but differ in defaults, presentation, and intent.
crewship recall <query>
The query is everything after the command name (joined with spaces). Server caps q= at 200 characters; longer queries fail fast with query too long: <n> chars (max 200).
Examples
Common errors
query too long: <n> chars (max 200)— server-side limit.bad --since: <reason>— value did not parse as duration or RFC3339.
See also
crewship journal— filtered tailing/audit, not question-answering.crewship activity— high-level cross-crew feed.crewship recap <chat-id>— agent-generated summary of one session.