Project memory and handoff
Your teammate never knew. Mneia captures the decisions a session produced at the moment work stops, and hands them to whoever picks it up next.
The problem
A developer works with Claude Code or Cursor for three hours on Monday. They establish twenty decisions along the way: why Postgres over DynamoDB, which auth pattern, which edge cases are out of scope, what broke when they tried the obvious approach.
On Tuesday they open a new session. The agent knows none of it. They spend the first fifteen minutes re-explaining.
Worse: mid-session, auto-compaction fires. The agent silently loses the constraint established two hours ago and confidently proposes the approach that was already rejected.
Worse still: a teammate picks up the work. The decisions live in a chat transcript that was compacted away, or in one person's head.
The artifact
Not a memory store you query. An object you receive, with every line marked by who asserted it.
Wire the retry path in charges/worker.rb to the new idempotency key. Nothing else is blocking.
Ledger writes are cut over and green in staging. Read path is still dual-reading.
Rollback flag payments.v2_reads is live and tested.
Three operations
At a task or day boundary, extract the decisions, constraints, and open questions out of the session. Detect contradictions with what is already known. Ask a human to confirm the load-bearing ones.
Explicit capture at a boundary, not ambient capture that produces noise.
Given the next task and a token budget, assemble the minimal high-signal slice. Not replay-everything, and not raw semantic search. Semantic search returns what is similar, not what is load-bearing.
Active constraints are always included, whatever the budget pressure.
Produce something a person or an agent receives: what is done, current state, open questions, constraints, next action. Provenance on every line, so the receiver knows what to trust.
The artifact, not a memory store you have to know how to query.
Where it runs
An MCP server that works in Claude Code, Cursor, Codex, or any MCP client. A CLI. File interop with the AGENTS.md and CLAUDE.md you already keep. Plus a deliberately thin web app for the things a terminal is bad at.
The inner loop stays in your terminal. A handoff that only works inside one vendor's tool is not a handoff, it is a session feature.
Access
We are onboarding teams in stages. Tell us where to reach you and we will get you set up.