Shipped is an SeaShell command that answers what did you get done this week from your actual history rather than your memory. Run /shipped and SeaShell reads your git commits and working sessions for the last 7 days, groups them, and writes a plain-language document to narrative/<window>.md in your repository. It is free, on by default, and needs no account. Four further sections fill in when SeaShell also has a record of what was said around the work.
What did you get done this week
The record of a week already exists across 2 places, your commits and your SeaShell sessions, and neither one reads like a sentence.
Shipped gathers both for a time window and renders them as prose rather than a commit list. There is nothing new to log, because it reads what is already there. The default window is 7 days, and --since changes it.
It writes markdown into your repository
Shipped writes 1 file per window, narrative/<window>.md, as ordinary git-tracked markdown.
The document is yours and portable: readable in any editor, diffable in review, and regenerated per window rather than maintained by hand. SeaShell keeps a rebuildable cache alongside it, but the markdown is the artefact you keep.
The sections it cannot fill, it names
Shipped renders 1 section from git alone, and names the 4 it cannot fill without more context.
Shipped comes from commits and sessions, so it always renders. Decided, Promised, Learned, and Scope changes come from meeting transcripts read by SeaShell Intake. When Intake is not connected, the document lists those four by name under a Not recorded heading rather than silently returning a shorter file.
Availability
Shipped is the 1 record engine included in the free SeaShell core, and it is available today.
It defaults on with no configuration and requires no account, though it does need a model provider configured, which SeaShell needs anyway. The Intake-backed sections belong to the paid tier, and SeaShell Pro is not yet on sale, so those four sections are not reachable yet.
Frequently asked questions
- Is the SeaShell work log available now?
- Yes. Run /shipped in SeaShell. It is part of the free core, on by default, and requires no account.
- What does it read to build the log?
- Your git commits and your SeaShell working sessions for the window. If Intake is connected it also reads the commitments, decisions, facts, and scope changes extracted from your meeting transcripts.
- Do I have to write anything?
- No. The log is derived from the record SeaShell already has and is regenerated per window, so there is nothing to maintain by hand.
- Where does the file go?
- narrative/<window>.md inside your repository, as ordinary git-tracked markdown. It is yours, and it stays readable and diffable without SeaShell.
- Why does my log say Not recorded?
- Because SeaShell has no meeting record for that window. Shipped is built from commits and sessions, while Decided, Promised, Learned, and Scope changes need Intake, which reads call transcripts and is part of the paid tier.
- Can it help with client status updates?
- It gives you the factual half: what actually shipped, in sentences. Shaping that into a client-ready note in a specific voice is a separate paid capability that is not yet on sale.
Try SeaShell in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install SeaShellRelated guides
Atlas with Code Llama (local via Ollama) in 2026
Explore Atlas with Code Llama (local via Ollama). Discover its 16K token context, free self-hosted pricing, and strengths for code infilling. Understand its tradeoffs for agentic work in 2026.
Atlas with Qwen2.5-Coder 7B (Ollama) in 2026
Discover Atlas with Qwen2.5-Coder 7B (Ollama), a powerful local model for terminal-native AI coding. Ideal for single-file edits and unified diff review, offering 32K context for free.
Atlas with Gemini 2.5 Flash in 2026
Optimize Atlas with Gemini 2.5 Flash. This workhorse model offers a 1M token context, reasoning, and low input costs ($0.3/Mtok), ideal for subagents and cost-sensitive tasks.
Atlas with DeepSeek Reasoner in 2026
In 2026, Atlas integrates DeepSeek Reasoner, offering powerful, cost-effective AI reasoning for complex coding challenges. Leverage its 1M token context window and advanced diagnostics at $0.14/$0.28 per Mtok.
Atlas with Llama 3.1 8B (Ollama) in 2026
Explore Atlas with Llama 3.1 8B (Ollama) in 2026. This self-hosted, free model offers a 128K context window, making it a strong choice for local AI coding agent workflows.
Atlas with IBM Granite 3.3 8B (Ollama) in 2026
Explore Atlas with IBM Granite 3.3 8B (Ollama) for local, free AI assistance in 2026. Leverage its 128K context window for summaries and subagent chatter, keeping code off third-party servers.
Atlas with CodeGemma 7B (Ollama) in 2026
Explore Atlas with CodeGemma 7B (Ollama), a free, self-hosted model ideal for precise code edits and fill-in-the-middle tasks. Leverage its 8K context window for local development.
Atlas vs Blackbox AI: Terminal AI Coding Agents in 2026
Comparing Atlas and Blackbox AI in 2026. Atlas offers terminal-native TUI, permission-gated tools, and local embeddings. Blackbox AI features /multi-agent dispatch and VS Code integration.