The state layer for the agentic era
Agents forget.
Yours won't.
Ouroboros turns your documents, your code, and everything your agents learn into a queryable graph on your own machine. The data stays yours — agents work on it in exactly the scopes you allow. Every claim grounded in a quote. Every write reversible. And what one agent learns, every agent you connect shares.
The problem
Every session starts from zero.
Watch any coding agent open a repo it has seen a hundred times: list the tree, read a dozen files, rebuild the same map it built yesterday — and pay for it again. Swap the repo for a contract stack or a folder of studies and nothing improves — every fresh session starts blind. Then the session ends, and all of it evaporates.
And the cost isn't just tokens. Every page of listing, grepping, and re-reading crowds the context window — and a crowded window poisons the agent: attention spreads thin, the actual task sinks into the noise, and hallucinations get likelier. The exploration your agent does to get oriented is the same thing that degrades it.
❯ glob src/**/*.ts 312 files ❯ read src/index.ts ❯ read src/router/mod.ts ❯ read src/db/schema.ts …mapping the same architecture it mapped yesterday… ❯ grep -rn "handleAuth" src/ ❯ read src/auth/session.ts 20 minutes in. Zero lines written. ── session ended · context discarded ──
The idea
Give them somewhere to put what they learn.
Ouroboros runs as a single daemon on your machine. Documents, repos, and agent observations are mined into typed entities, quoted facts, and resolved symbols — a graph that outlives every session. The next question costs a query, not a re-read.
It works on whatever your work is made of. A folder of whitepapers and studies your agents should actually know. A company's SOPs, contracts, and policies. A year of tax filings and statements. A client's case file. A monorepo. If your agents keep re-reading it, it belongs in the graph.
Your agents work for you. Sophia works for them — persistent memory, a grounded source of truth, and a coordination substrate underneath everything they do.
How it feels
The same task. Twice.
One question, asked two ways. Without a state layer, the agent re-reads the source and forgets by tomorrow. With one, the answer comes back in milliseconds — with the verbatim quote it stands on.
❯ "what did we decide about the lease escalation clause?" ❯ read commercial-lease-2024.pdf (212 pages) …reading… …still reading… …still reading… "Escalation is capped at 3% annually…" ~60k tokens · minutes later · forgotten by tomorrow 58k irrelevant tokens now poisoning your agent's context
❯ sophia.search("what did we decide about the lease escalation clause?") 1 fact · 212ms "Escalation capped at 3% annually, renegotiated at year 5." source: commercial-lease-2024.pdf, p.14 — verbatim quote, substring-checked next morning, fresh session: ❯ sophia.catch_up() since yesterday: 2 documents mined · 1 correction you made · 3 open questions oriented in one call. no re-reading.
Token counts illustrate the pattern on a 212-page document; the 212ms query is a measured figure from the live instance.
The first call
Every session starts oriented.
The first thing any connected agent calls is orient — and
it comes back knowing what you were working on, what changed, and what
to do next. Agents notice. These reactions are quoted verbatim from
real sessions:
❯ sophia.orient() sync_status: 31 entities · 6,566 docs · 6,476 facts hot_entities: OR (1,048) · Inbox (32) goal_stack: 'C3a security core — paused at Task 7' next_likely_calls: coordination_inbox · catch_up · list_unmined_documents fully oriented. one call. ~1,800 tokens.
sophia.orient gave useful startup context in one call: connection identity, scope, data counts, mining status, goal stack, hot entities, recent corrections, next likely calls, SDK quick-start, and coordination state. Codex dogfood session, 2026-05-10
Why it matters: this is exactly the kind of state a fresh agent would otherwise reconstruct with repeated repo reads, document searches, and ad hoc chat context. Codex dogfood session, 2026-05-10
Under the hood
No magic. Mechanism.
There is no single trick. There are hundreds of small, deliberate ones — each saving a round-trip, a re-read, a wrong answer — and they multiply. A few of them, briefly:
None of this is revolutionary. All of it together is.
Sovereignty
All of it on your machine.
One local daemon. Files on disk you can open in Obsidian without us. Agents connect only through scopes you mint, every read is logged, and every write can be rewound. No account. No cloud copy. No silent fallback to somebody else's model.
Get it
Be there when it opens.
The source opens when it's ready. Leave an email and you'll hear about it exactly once — or go deeper into how the system works right now.