Every session ends.
The work shouldn’t.
You close Claude. A teammate takes over. Another agent starts working. You come back two days later.
The conversation is gone. The reasoning is scattered. The project has moved on.
So someone has to reconstruct what happened.
- Re-reading old chats to find what you decided.
- Explaining the project to an agent that already investigated it.
- Asking a teammate what happened while you were out.
- Rebuilding context you had a week ago.
The work continues. The understanding doesn’t.
The missing piece isn’t more context.
It’s the project’s own intelligence.
A bigger context window hands the model more transcript to re-read. Memory keeps pieces of the conversation. Neither one restores where the work actually is.
The project needs its own persistent intelligence — an understanding of what it is, what happened, what was decided, what’s still open, and what comes next.
The project knows where it stands.
Sessions end. What Auric keeps is the state between them — the decisions and the reasoning behind them, what’s still open, and the next move.
Your code and commits are the evidence of what changed. The record is what says where the work stands — and it holds only what you or your agent wrote to it.
What ends
What continues
It’s not just shared context.
It’s shared understanding.
The next person doesn’t just need the files. They need to understand why the project is where it is.
- What changed?
- Why?
- What’s still open?
- What happens next?
Understand.Continue.
You shouldn’t have to be the person who started the work.
Once the project carries its own understanding, continuing it stops depending on who happens to remember everything.
Today
- You come back a week later and keep going.
- You continue in a different tool, from the same state.
Where this goes
- A teammate continues from where you stopped.
- An agent continues from the project’s current state.
Local-first. The record is a file in your workspace — there is no server holding it, and it goes nowhere you don’t send it.
Whoever opens the project next continues from where it stands.
- Gitkeeps the files, and how they changed.
- Chatkeeps the conversation you had.
- Aurickeeps the state of the work between them.
For the technically minded
- Local-firstThe record is a single file on your machine. Offline by default.
- No AI in the read pathRestores are data assembly. Same file in, same context out.
- Append-onlyNothing is edited away. Decisions are superseded, with the when and why.
Runs inClaude Code · Any MCP client · Auric CLI
The beta is open.
The software is built and running. Access is granted as capacity allows, so the projects already on it stay properly supported.
The work is already moving.
Don’t be the next person reconstructing it.
Join the betaWe review and grant accessYou get an email
— The Auric team