This memory is worth keeping.
I want to switch AI assistants without starting over.
When I work with an assistant, I spend time explaining my projects, my constraints, my preferences and the reasons behind my decisions. Through exchanges and corrections, it comes to understand how I work.
In practice, this context is everything I no longer need to repeat: a project’s vocabulary, the options already ruled out and why, the level of detail I expect, the checks I insist on. An assistant that knows it starts from the right place. One that does not makes me explain everything from the beginning.
This context represents hours of work. If it stays locked in with one provider, I lose part of my freedom. The price may go up, another AI may become more relevant, the service may stop suiting me — and yet I will hesitate to leave, because everything would have to be explained again.
Some assistants already offer built-in memory. It is convenient, but it lives with their vendor: another assistant cannot reach it, and I am not the one who controls how it is kept.
My goal: for this memory to follow me. I want to be able to move it, reuse it with another assistant and back it up myself.
Without a harness
With a harness
Switching tools should remain a choice. It should not mean starting over.
In short: three building blocks.
I call this whole setup my harness (as in a harness you strap on): the working environment that connects my assistants to my files, my memory and my applications. It rests on three building blocks.
- Files. My documents and their successive versions are tracked with Git and hosted on GitHub.
- Memory. Decisions, their reasons and project progress are kept in Hindsight, a memory service I host myself.
- Access. Connections to my applications (email, documents) go through Activepieces, a gateway I also host.
How to read this feature. Chapter 2 shows the handoff in practice. Chapters 3 to 5 detail each building block. Chapter 6 follows the path of a piece of information, and chapter 7 takes stock. A glossary at the end covers the technical terms.
What I host myself, and why.
I host two building blocks on a server I administer: the memory, which holds my context, and the gateway, which holds the access to my applications. Entrusting the only copy of one, or all the access of the other, to one more online service (a “SaaS”) would create a dependency I prefer to limit.
This is not a judgment on the security of those services: an online service can be well secured. My choice is about what I want to be able to decide myself: where information is kept, who is involved in processing it, how to retrieve my data and how to withdraw access. In return, running these two building blocks is my job, with the responsibilities that come with it.
Not everything is on my side, though. My files are on GitHub — a deliberate exception, which I explain in chapter 3. I also use assistants hosted by their vendors, Claude through its API (called directly by a program, without going through a conversation) and my cloud applications. I am not trying to make these dependencies invisible: I am trying to identify them and to be able to leave them.
