Your last session cost
597,000 tokens a step

Ninety-seven percent of that was re-reading its own history. An AI coding session charges you for its whole transcript on every single request: ask a one-line question and you pay for all of it, run an agent loop and you pay for all of it once per command. Nothing tells you until the limit is gone at 2am, mid-deploy.

Sealkeep already holds your session files, so it can answer the question nothing else can. One command, local files only, no account needed.

$ sealkeep meter
Context cost, last 24h, across 36 sessions.
Read from local session files. Nothing left this machine.

tool   where              steps  per step  history  total in  signals
claude bot                  457      597k      97%    272.8M  BLOATED
claude sometest             368      474k      96%    174.3M  BLOATED STALE
codex  spala                581      162k      99%     94.2M  BLOATED STALE POLLING

Total sent: 807.8M. The same work from fresh sessions
carrying a 3k-token pack: about 36.5M.
That is roughly 771.4M spent re-reading, 95% of everything you sent.

Real output from one machine, one morning. The meter reads local session files. No recovery phrase, no key, no network, nothing uploaded to produce a number.

Resuming an old session is
the expensive mistake

Pick up a months-old conversation to ask two questions and the entire transcript goes with every request. One real evening, two questions on a resumed session cost 41 million tokens, of which about 220,000 were the actual work. The weekly allowance was gone by 2am, mid-deploy, and nothing had said a word.

Sealkeep gives you the other option: leave the session, keep what it knows. One command prices the choice, writes a small pack of where the work got to, and hands you the command to start fresh.

$ sealkeep fork
The most expensive session you have open is the claude one in bot.

  carrying on there      615k tokens per step, 97% of it re-read history
  starting fresh          22k tokens per step, carrying a 392-token pack instead
  you would save         593k tokens on every step from here on

The full session is sealed and searchable, so nothing is lost by leaving it.

Three signals, each one true of a session
that ended somebody’s week

Each threshold is deliberately boring, and each one fired on a real machine the night two limits died two hours after they reset.

It never tells your session
the same thing twice

Sealkeep used to re-send the same preamble and the same list of preserved sessions after every prompt and every Bash, Edit and Write. Measured on one real session, 80% of everything it injected had already been given to that same conversation, and because a block added early is re-sent on every request that follows, the repetition cost 81.6 million tokens.

Answered, not dodged

One command, reads local files only. It tells you which session to abandon and what that will save. The number is the pitch, and it belongs to you.

The order is the safety property

Nothing is reclaimed before it is verified. Nothing is verified before it is sealed.

$ sealkeep autopilot --reclaim
✓ vault created 7a126017…        ✓ recovery phrase shown — 24 words · once · not stored
✓ hooks installed — claude, codex   preserve + upload automatically · reclaim explicitly enabled

$ sealkeep autopilot status
sealed 412 · verified 412 · reclaimed 3.4 GB
last cycle 40s ago · next in 5m

Autopilot preserves, indexes, and uploads on a loop. Reclaim joins that loop only after you explicitly enable it, and Sealkeep notifies you when disk is reclaimed or something needs a decision — never for routine sealing, which would only train you to ignore it.

Six months of reasoning,
still searchable

Twenty-four words,
not a base64 string

Words survive bad handwriting, can be read aloud, and carry a checksum — so a misread word is caught and corrected rather than silently locking you out.

Whose bucket

Not the same product with a different quota. On free, archives go to a bucket you own under your own credentials — we never hold them and cannot count them.

Or skip storage entirely and keep everything local — Sealkeep still seals every archive, it just has nowhere to copy it.

What ships now,
and what advances next

Production capabilities today, with dated milestones for the next assurance gates.

Independent-review preparation is active. Encryption format v2 uses published authenticated-encryption primitives and ships with deterministic vectors plus byte-by-byte tamper coverage. The public assurance roadmap tracks external cryptographic review as the next gate; no completed third-party audit is claimed today.

The ones that actually matter