SeaShell Commitment Tracking reconciles what you told a client you would do against what is actually in the repository. It takes the commitments extracted from your calls and checks them against your code and commit history, then sorts them into 4 states: open, delivered, at-risk, or ambiguous. At-risk means a promised date passed with no matching work. The engine ships in SeaShell today behind the paid tier, and SeaShell Pro is not yet on sale.
Promised on a call, lost by Friday
The commitments you make on a call live in 2 places, a transcript and your memory, and neither is near the repository.
Commitment Tracking treats each commitment as a claim and the codebase as reality. The gap is the point: a promise with matching code is delivered, and a promise with no matching work and a passed date is at risk and worth your attention now.
Evidence from code and commits
SeaShell checks each commitment through a 2-tier deterministic cascade before it spends a single token.
Tier 1 looks for an explicit target actually present in the codebase index. Tier 2 does a keyword match against the index and against recent commit messages and paths. Both are deterministic, so the routine pass costs nothing to run. Every verdict carries the evidence behind it rather than arriving as a bare judgement.
Semantic matching is opt-in, not automatic
A promise fulfilled in different words than it was made in needs 1 extra step, and that step is deliberately manual.
The deeper LLM judgement that catches paraphrased delivery runs only when you ask for it with --deep. The background pass stays deterministic and token-free, so a low-confidence match is flagged rather than assumed. You decide what counts as delivered, and a commitment you confirm as delivered never silently downgrades on a later check.
Availability
Commitment Tracking is 1 of the 8 record engines in SeaShell, and it sits behind the paid tier.
The engine is built and running in the product, gated to SeaShell Pro. Pro has no checkout yet, so it is not something you can buy today. It also depends on Intake for its input, since the commitments come from call transcripts. Shipped, the automated work log, is the one record engine available free right now.
Frequently asked questions
- Is SeaShell commitment tracking available now?
- The engine is built and running in SeaShell, but it sits behind the paid tier and SeaShell Pro is not yet on sale, so you cannot purchase access today.
- Where do the commitments come from?
- From the commitments SeaShell Intake extracts from your call transcripts. Email as a second source is designed but not built.
- How does it know something was delivered?
- A two-tier deterministic cascade: an explicit-target check against the codebase index, then a keyword match against the index and recent commit messages and paths. Each verdict carries its evidence.
- What does at risk mean?
- A commitment whose promised date has passed with no matching code or commits, so it needs your attention now rather than at the next client call.
- Does it use an LLM on every check?
- No. The routine pass is deterministic and spends no tokens. The LLM judgement that catches paraphrased delivery runs only when you pass --deep.
Try SeaShell in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install SeaShellRelated guides
Atlas for Svelte in 2026
Adopt Atlas, the terminal-native AI coding agent, for Svelte and SvelteKit projects in 2026. Enhance development with intelligent code search, secure local embeddings, and guided code generation.
Atlas with MiniMax-M2.1 in 2026
Drive Atlas with MiniMax-M2.1 in 2026. Leverage its 204,800 token context and cost-effective $0.30/Mtok input for powerful code search and reasoning capabilities.
Atlas with Llama 3.1 8B (local via Ollama) in 2026
Explore Atlas with Llama 3.1 8B (local via Ollama) for on-device AI coding in 2026. This 4.9GB model offers a 128,000 token window and runs free, self-hosted.
Atlas with Gemini Flash Latest in 2026
Explore Atlas with Gemini Flash Latest, Google's fast, rolling AI model. Ideal for dynamic teams in 2026 seeking an always-current coding agent with a 1M token context.
Atlas with Magistral Medium in 2026: Deep Reasoning for Complex Code
In 2026, Atlas developers can leverage Magistral Medium for deep, multi-hop root-cause analysis across services, utilizing its 128,000 token context window.
Atlas with Qwen3-Coder 480B-A35B Instruct in 2026
Explore Atlas with Qwen3-Coder 480B-A35B Instruct, Alibaba's 480B parameter coding model. Ideal for agentic SWE-bench tasks, offering a 256K token context window for complex codebases.
Atlas with DeepSeek V3.2 (open weights) in 2026
Drive Atlas with DeepSeek V3.2 (open weights) in 2026. Leverage its 160K token context window and ultra-low $0.38/Mtok output cost for efficient AI coding.
Atlas with Mixtral 8x22B (local via Ollama) in 2026
Drive Atlas with Mixtral 8x22B (local via Ollama) in 2026. This 80GB self-hosted model offers a 64,000 token context window, keeping your code local and costs free.