Who Owns What Your Agent Knows?

Who Owns What Your Agent Knows? | SafiwareWho Owns What Your Agent Knows? 05 Jul, 2026 Most days, I work with capable agents. The strange part is not that they forget. That will get better. The stranger part is where the remembering happens. One agent helps me reason through a paper. Another edits code. Another has the meeting notes. Another knows the failed attempt. Over time, each agent learns a slice of how I work. That is useful. It is also the problem. If the record of my work lives inside one agent, then my process becomes part of that agent’s product. The agent is no longer just helping me use my process. It is becoming the place where that process lives. The model is not the only thing that matters. The layer around the model matters too: the context it sees, the memory it keeps, the tools it can use, the skills it loads, the project instructions it follows, and the way it turns yesterday’s work into tomorrow’s default. Call that the harness. At first, that feels like the product getting better. I do not think that anymore. Now ask the question: If I leave this agent tomorrow, what leaves with me? Do the memories leave? Do the lessons leave? Do the workflows leave? Do the review habits leave? Do the conventions leave? That is the ownership test. The Repo Is Not Enough The obvious objection is simple: put the context in the repo. Yes. For code, the repo should carry a lot: ADRs, docs, tests, comments, decision files, and project instructions. If a decision belongs with the code, put it there. But the repo is one view of the work, not the whole work. It does not hold the client meeting, the cross-project habit, the private note, the research trail, or the way five tools were used together. It cannot find the sentence you said in a meeting. It cannot find the convention that lives only in your head. Some of that should be written down. Some of it should never live inside one provider’s memory. So you supply it. You are the missing layer. That is fine once. It is not fine as a system. The work you keep carrying is not random context. It is your process. It is how you make decisions. It is the shape of your taste. It is the difference between an agent that can do work and an agent that can work with you. And right now, most of that know-how is either trapped in your head or scattered across vendor-specific harnesses. Not Just The Model The popular story says the model is the product. That is partly true. Better models matter. A lot. A good harness does not rescue a bad model. But the wrapper changes the result in ways that are not cosmetic. The useful evidence is messy in the right way. In SWE-ContextBench, oracle-selected compact summaries improved coding-task resolution from 26.26% to 34.34%. Raw trajectories barely helped. Mem0 underperformed the no-context baseline. So the point is not “more memory.” More memory can make things worse. I also dislike the word memory here. It points backward. This layer also holds decisions, workflows, open questions, failed attempts, and ideas still worth trying. Memory is too small. Know-how is closer. But know-how does not mean dumping everything into a bigger memory store. Own the raw record. Curate the useful views. Keep the source attached. Make derived views disposable. That is the know-how layer I mean. Memory Islands The opposite of that layer is what we have now. The MemOS paper calls them memory islands: ideas explored in one environment do not carry cleanly to another, so you rebuild context by hand. That is exactly what daily agent work feels like. Claude knows one slice. Codex knows another. Cursor knows another. Pi knows another. Your notes know something. Your commits know something. Your meetings know something. Your calendar knows something. No one view has the work. The fix is not to give one vendor every slice. That only makes the island bigger. The fix is to own the layer that connects them. I want a know-how layer outside any one agent: an owned record of what happened across the agents, tools, people, decisions, and artifacts involved in the work. Not one vendor’s memory. My layer.

The know-how layer stores records and governance rules that let agents and human views access only the parts they need. The Black Box This is where the argument is easy to misread. The point is not that every vendor is secretly training on every conversation. Some consumer products can use your chats or coding sessions for training unless you opt out. Business products usually draw a harder line. OpenAI says it does not train on business data by default. Anthropic’s commercial terms say it may not train on customer content. Policies vary by product, tier, and date. These are current product promises, not ownership. The deeper problem is control. My work sits inside systems I do not control, under policies I do not set, in formats I may not be able to inspect, correct, export, or move. So I do not really control the...

Who Owns What Your Agent Knows?

Related Articles

(no title)

Scientists reverse brain aging, with a nasal spray

AI has torched the market for junior programmers

Al Vigier: Canada's AI strategy shouldn't include secret Palantir bills

The Anatomy of an AI-Native Org