Use cases / Solo developer
Local mode is shipped today: one SQLite file, no account, and continuity that survives closing the session and switching the tool. Cross-device sync and the one-line installer are planned, and this page says so where they come up rather than at the bottom in small type.
You switch from Claude Code to Cursor and the context evaporates. Each client keeps its own machine-local, unverified scrap of what happened — or invents a confident replacement for it.
On the left, what a week-old decision looks like without a ledger. On the right, the record Zephr keeps — the claim, the file it rests on, the date, and the review state, all still attached.
The answer is somewhere in a Claude session you closed, or a Cursor thread you did not save, or a note you meant to write. Whatever the next agent tells you about it will sound equally confident either way, which is the actual problem.
The implicit flow was rejected because the client cannot hold a secret, so a code interception without PKCE is trivially replayable.
Any connected tool can recall this — and if src/auth.md changes, the anchor is reclassified before the claim is served again.
Illustrative example — not live data
Clone the repo, build from source, connect a client, and start capturing provenance-backed memories. Four of the six capabilities below are shipped; the two that are not are named here rather than discovered later.
SQLite-backed beliefs with provenance, confidence, and revision chains. One file on disk, no account, no egress.
core evidence graph · ADR-012
An Ed25519-signed, single-use continuity packet carries a decision between sessions and tools. The signature covers the citations, not just the claim.
Slipstream v1 · E2E-proven on main
Deterministic, CI-blocking tests for retrieval, scope, and contradiction behavior. You can run the trust claims yourself rather than take them on faith.
deterministic suite · ADR-013
Consented MCP configuration for both clients. Zephr reads what it is handed; it does not scrape private editor state.
client-adapters package
The one-line install path does not exist yet. Today the entry point is cloning the repo and building from source.
golden path designed in the Connect cluster; not built
Resuming on a second machine under the same account requires the managed cloud, which is still gathering evidence.
gated on the ADR-010 tenancy gate
npx distribution and cross-device sync are documented in the roadmap and are not available today.
The same golden path that drives /how-it-works, reframed for one person moving between tools on one machine.
Hand a decision to zephr_remember with its source and anchor. It enters your local evidence graph as a dated, cited record — not a summary in a black box.
Open Cursor against the same admitted worktree. The continuity packet carries the decision across, and the receiving agent verifies the signature before trusting it.
zephr_recall shows why a result came back: which files, which commit, which review state. When nothing clears the bar it abstains and says what is missing.
Build from source, connect your first client, and capture a memory. Nothing on the roadmap has to land before the product is useful to one person.