Agent work should outlive
the session it was done in.
This page is the full case for OpenLotus: the mission, the vision, and every class of evidence behind them. Community threads, research papers, blogs, write-ups, and the platforms' own documentation. Each claim is cited so you can check it. None of the numbers are ours.
Mission
Give every project a durable, harness-neutral record of why the work is the way it is.
Sessions stop starting blind. Decisions stop dying in chat logs. Constraints stop being rediscovered the expensive way. The record is one shared ProgressMap, read and written by any agent through a CLI and MCP, and shown the same way to the human on a dashboard. Memory is an implementation primitive. Durable state is the product.
Vision
Agent work with the durability of code itself.
Git answers what changed. OpenLotus answers why. Every project's decisions, constraints, lessons, and drift live in a record that outlives any editor, harness, or model. Switching tools costs nothing. Starting a session costs nothing. Shipping a completion claim without evidence feels as wrong as deploying without tests.
Evidence, class by class
What the community already knows.
Four recurring patterns from r/ClaudeCode and r/ClaudeAI threads through 2026, distilled, with dates attached. We did not run these threads. We read them. Matching complaints appear on X, three of them linked from the landing section and listed in the bibliography below.
r/ClaudeCode and r/ClaudeAI, 2026
Sessions start blind
Tens of thousands of tokens burned from zero every single time. A March 2026 thread measured 69.2K tokens (34.6% of a 200K window) loaded before a single character was typed, and rule re-injection eating roughly 46% of context after 30 tool calls. February 2026: the agent does not know you always grep first, read the test file, then edit, so you fix the same mistake session after session.
r/ClaudeCode, 2026
Agents undo each other
Run a second agent and it re-litigates settled calls, rewrites functions it does not understand, and reverses the first agent's work. The complaints name no clean number for the rework cost, and we will not invent one. What the threads establish beyond doubt is that the work is not durable between sessions, so nothing stops the next session from disagreeing with it.
r/ClaudeCode, Oct 2026
Context gets dumped, not structured
One launch post measured the industry habit precisely: 6,000-token conversation dumps replaced with roughly 400-token structured cards, at equal usefulness. The problem is not that agents lack context. It is that context arrives as undifferentiated history instead of a record.
r/ClaudeCode, 2026
The harness itself flags the waste
Claude Code's own /context panel reports roughly 22.8K recoverable tokens per session spent re-reading files that were already read. The tooling is telling on itself: nothing carries forward what was already learned.
Research papers and studies
The measurements agree with the complaints.
Every figure below was measured at equal or better task-success rate. That rule is not ours; it is the field's, and we follow it.
ContextSniper report, arXiv 2607.01916, Jul 2026
On matched 50-task SWE-bench Lite conditions, replacing repeated exploration with compact memory cut total tokens 51.5% (OpenClaw) and 38.9% (Claude Code), with cost down 36.4% and 27.3%, and resolution rates unchanged.
What it means for us: The single largest measured waste in agent work is re-reading, and removing it does not hurt accuracy. A record is the cheapest possible fix: read once, write once, never re-derive.
Sam-Bodden study, SWE-bench Verified
A resolved issue costs 19K context tokens with a compressed representation versus 94K with full-file dumps, at the same resolve rate.
What it means for us: What you store and how you store it matters more than how much you store. Durable state beats bigger windows.
Mem0 measured comparison, Sep 2026
Retrieval-based memory used 166 prompt tokens versus 594 for naive history (72% saved) at equal answer quality, and under 7K versus roughly 115K under full-context loading (about 16x).
What it means for us: Structured, retrieved memory is an order of magnitude cheaper than replaying the conversation. This is the cost shape OpenLotus is built around: small reads from a whole record.
Xu, iso-accuracy caveat, Jun 2026
Token savings are only meaningful at equal task-success rate. A method that saves tokens by failing earlier saved nothing.
What it means for us: We inherit this rule. Every waste figure on this page was measured at equal or better resolve rate. Savings on first attempts are not claimed. Savings on repeated work are.
Blogs and write-ups
The practitioners converge on the same shape.
Lakhina, ACP analysis, Medium, Sep 2026
The Agent Client Protocol forwards MCP servers across harnesses but carries no instructions field. Each harness still reads its own file (CLAUDE.md, AGENTS.md, GEMINI.md).
What it means for us: Memory that lives in MCP plus a shared rules file ports everywhere. Memory that lives inside one harness does not. Harness neutrality is a protocol position, not a feature flag, which is why it cannot be copied in a weekend.
Lanham, multi-harness households, Medium, Jul 2026
Households running Claude Code and Codex as architect, builder, and critic are now standard practice.
What it means for us: People already work with several agents on one project. The record has to be the thing they share, or they are running several projects by accident.
HyperStack launch post, Oct 2026
6,000-token context dumps replaced with roughly 400-token structured cards.
What it means for us: Even early adopters converge on the same shape: small structured units of durable state, retrieved on demand.
Platform publications
The vendors already prescribe the discipline. They just do not automate it.
The full conversation is re-sent every turn. Compaction summarizes under pressure, at what the docs call the model's least intelligent point. The official guidance is to write down what matters and start clean.
What it means for us: The platform's own answer to context decay is a human discipline: write things down. OpenLotus is that sentence, automated, shared, and enforced with evidence.
Claude Code /context panel
Roughly 22.8K recoverable tokens per session attributed to file re-reads.
What it means for us: Re-reading is visible in the tooling. Carrying forward is not, because nothing exists to carry it.
Claude-Master-Skill token-budget documentation
A 200K window is effectively 120 to 140K usable before typing starts. Subagent delegation can turn a 12,000-token read into a 200-token answer.
What it means for us: The budget is smaller than advertised, and the fix is delegation over shared state, not a bigger window.
Analysis
Each tax, and the primitive that answers it.
The four taxes are not marketing buckets. Each one is a measured or strongly evidenced cost, and each maps to exactly one of the product's four primitives. The numbers behind each row are cited in the sections above.
Tax
Measured cost
OpenLotus primitive
Evidence status
The re-exploration tax
Up to ~50% of tokens
State and lessons: decisions, patterns, and diagnoses written once, read by every future session.
Measured in the studies above at equal accuracy.
The pre-loaded context tax
A third of the window before work starts
Reality: the ProgressMap is sensed from git, not re-explained by the agent. Sessions start from the record, not a repo scan.
69.2K measured pre-load; structured memory reads at ~166 tokens.
The rework tax
Every avoided re-run is a session not burned
Drift: deterministic reconciliation of declared versus observed state, with evidence. Completion claims without evidence surface before the next agent trusts them.
Directional from the community record; we publish no invented percentage.
The lock-in tax
Memory dies when you switch harnesses
A harness-neutral record via CLI and MCP: 23 tools any agent can call, plus a shared rules file that ports by construction.
Structural: ACP carries no instructions field, so neutrality lives in where the record lives.
Limits
What we deliberately do not claim.
No invented rework percentage
The community record is loud about agents undoing each other, but no clean third-party number isolates rework cost. We refuse to fabricate one. Our honest claim is narrower: every avoided re-run is a full session not burned, which rests on the measured re-exploration numbers above.
No token savings line yet
We will not say "save X% of your tokens for $19" until the X is ours, from our own paired A/B: same repo, same tasks, with and without OpenLotus. The reminder is written into our internal research log so it cannot be quietly forgotten.
No savings without accuracy
Following the iso-accuracy rule from the literature: we only count waste avoided on repeated work at equal task-success rate. A cheaper failure is not a saving.
Sources
The bibliography.
Papers and studies
ContextSniper report, SWE-bench Lite, Jul 2026. Re-exploration token study.
arXiv 2607.09691, SWE-bench Verified. Compressed representation resolves at 19K context tokens vs 94K for full files, same resolve rate.
Token optimization playbook, Sep 2026. Retrieval memory versus history dumps.
arXiv 2608.13568, Jun 2026. Token savings only count at equal task success (iso-accuracy); a method that saves tokens by failing earlier saved nothing.
Community
Threads, 2026. Pre-load measurements, drift complaints, rework reports.
Jun 2026. Agents forget everything when the terminal closes; the morning re-explain tax.
Apr 2026. Coding agents have a context problem, not a model problem.
Sep 2026. A model can hold 1M tokens and still meet you for the first time every morning.
Blogs and write-ups
Lakhina, ACP analysis
Medium, Sep 2026. No instructions field across harnesses.
Lanham, multi-harness households
Medium, Jul 2026. Architect, builder, critic workflows.
HyperStack launch post
Oct 2026. Structured cards versus context dumps.
Platform publications
Conversation re-sent every turn; compaction under pressure; start-clean guidance.
Claude Code /context panel
And Claude-Master-Skill token-budget documentation. Re-read waste and usable-window figures.
Where an exact permalink was not verifiable, the source is named with author or community and date instead of linked. We would rather cite loosely than link dishonestly.
One record. Every session. Any harness.
That is the mission, and the evidence above is why we are certain it matters. Pair a repo and your next session starts from the record.