What we believe about the sessions you keep losing.
Six positions we are not willing to trade away.
Your repository remembers the code. Nobody remembers the reasoning.
A session is where the thinking happened: the wrong turn, the constraint nobody wrote down, the reason that function looks strange. It exists once, in one tool, in a format only that tool reads. Then it is gone.
We are not building a place to work. We are building the layer beneath the places you already work.
No new IDE, no environment to adopt, no surface your team has to live in. Stay in your tools. A small daemon watches, syncs, and serves session memory in the background. That is the whole product, and we intend to keep it that small.
A code graph can be rebuilt from the repository at any time. Session history cannot.
Indexing tools tell an agent what the code is. Sessions are the only record of why it is that way: the option ruled out, the constraint discovered at 2am, the fix that made another fix unnecessary. Delete them and that reasoning is gone for good, which is exactly why we treat them as infrastructure rather than scrollback.
A summary is a rumor. History is a fact.
When a session crosses from one agent to another, Motif writes the target tool's own session format and registers it in that tool's own state. Codex resumes it as a Codex session, because it is one. Anything less is pasting a paragraph into a prompt and hoping.
Agent sessions contain your codebase, your keys, your half-formed decisions. Too intimate for somebody else's cloud.
Open source, Apache-2.0, self-hosted from the first commit. One process, one SQLite file, no telemetry, no third-party call except the model provider you choose yourself. Filtering and secret redaction run on your machine before anything uploads. Delete the folder and we never knew you.
A motif is a pattern that recurs. So is good engineering.
Every session your team runs is a thread. Alone, each is noise. Collected, they resolve into the shape of how your team actually builds: the files that matter, the decisions that stuck, the ones that were superseded.
Every session teaches Motif, so every agent and teammate arrives already knowing your codebase.
← back to the pattern