An agent that
outlives every model.

Every model you have ever used has forgotten you. The window closes, the session ends, the next morning begins with the same explaining. You teach the same context to the same blank assistant, day after day, and you pay for the teaching every time.

We accepted this because the alternative looked like a research problem. It is not. It is a product problem. The model is one piece of the partner. It is not the whole partner.

A partner is the thing that knows you. It carries forward what was learned yesterday. It picks up where the last session ended. It recognises the codebase, the project, the person. The model underneath can be swapped for a faster one, a cheaper one, a smarter one, and the partner does not blink.

What the partner is

It is not a wrapper around a chat window. It is a continuity layer that sits between you and whichever model is in fashion this quarter. The memory is yours. The identity is yours. The keys are yours. The model is rented from someone, and that is fine, because the partner is the part that stays.

When the next model lands, the partner does not start over. It keeps what it knows about you and tries the new brain underneath. If the new brain is better, you get the upgrade. If it is worse, you swap back. Nothing about you needs to be re-explained either way.

Why this matters now

The model market is going to keep churning. New releases every quarter. Old ones deprecated. Prices rearranged. Capabilities shuffled. The cost of staying current, measured in re-teaching, is about to become the dominant line on every AI bill.

The teams who win the next decade are not the ones who pick the right model. They are the ones who own the partner that lives above the model. The model is a commodity. The partner is the relationship.

What stays yours

What it learned about you, your code, your project, your taste. The keys it uses to act on your behalf, sealed by your operator key, never seen by the model. The machine it runs in: signed, isolated, on your hardware, with a switch you control. The protocol it speaks: open, stable, portable.

None of these are provider-bound. None of them ride along with the model. When the model gets replaced, all of this stays.

Where we are

The partner runs today on the maintainer's machine. Persistent memory across sessions. Model-swap survival. Operator-bound key vault. Sealed runtime. It already does the thing it was built to do; the first cohort goes out for the people who will help shape what “already knows you” looks like in their work.

If you want one, ask. The first cohort is small on purpose.