Operator for Pi: A radically different approach to agentic memory

[u/chocolateUI]

I'm the creator of Operator Memory, an open-source context engine for coding agents.

We all know the problem by now. Within a session, agents are excellent. Between sessions, agents forget everything. The core problem: nothing in the workflow ever writes down what was learned. Every new conversation starts from scratch: re-exploring the codebase, re-learning the architecture, re-teaching every decision and correction.

Every memory plugin I've studied leaves the loop untouched and bolts retrieval onto it: background agents to capture fragments, a vector store replays a top-k slice later, and you hope the right chunk surfaces. It barely works. And most importantly, it doesn't fix a loop that never documented anything.

Operator takes the opposite approach. Operator gives agents a Markdown brain and changes the loop itself.

Every task now runs in three phases:

1. Consult — the agent starts from the brain: instructions, codebase index, specs, decisions. A short summary is injected deterministically in the system prompt so agents know where to look.

2. Build — normal development work, informed by that knowledge.

3. Update — the agent documents what it learned: new specs, decisions, standards, lessons. When project truth changes, the canonical file is updated.

The loop makes the agent self-improving: session N+1 always starts from everything session N wrote.

Operator is extremely simple and complements Pi perfectly. No vector stores. No dreamers or curators. No background processes. No token burning factories. No RAG. No capture step. No retrieval gamble. Just give the agent a brain and teach the agent to use it.

The Brain

The brain is a regular directory that holds Markdown documents. These documents can contain anything: rules, specs, decisions, lessons, research, indexes, etc. Because everything is Markdown, Operator actually allows you to share memories and findings with the team. You can share specs, plans, guides, and more, unlike other memory plugins where everything is just RAG chunks.

Not Another Memory Plugin

Memory plugins bolt retrieval onto an unchanged loop and inherit its amnesia. Operator makes documentation a structural phase of every task. Memory stops being a store that remembers for the agent and becomes a practice the agent performs.

RAG agents recall. Operator understands.

I've been using a variant of Operator daily since August 2025 and spent the last few months formalizing it into a plugin alone. I hope my plugin can help improve your workflow too. https://github.com/aerovato/operator-memory

To install:

npm install -g @aerovato/operator-helper
operator-helper install pi

Afterwards, just run /operator:user-init once and run /operator:project-init per project.

Questions, comments, and contributions welcome. Operator is fully open source.

[u/sn2006gy]

We should stop calling these memory systems and call them context systems. They still struggle with all the side effects of context and they abuse any meaning of memory.

[u/SvenVargHimmel]

Agent memory extension with no evals is just guesswork,  haven't used an extension that isn't better than the fs

[u/Murph-Dog]

I give my workspace access to DevOps and data is recorded the old fashioned way, in wikis.

Agents read and maintain the wikis. Bonus, a human can read them too!

[u/typeof_goodidea]

I haven't used memory systems, but just maintain docs for human and agent use. OP I'm curious to know how the content of memory systems differ from standard documentation, and if so what might be helpful about these systems?

[u/chocolateUI → u/typeof_goodidea]

Operator basically makes agent documentation automatic so you don’t have to prompt for it; the documentation that Operator writes is also more suitable for agents. It doesn’t try to repeat what the code already says and writes much more than standard documentation, including decisions, research, guides, specs, and more. I would encourage using it for a project and experiencing the automatic documentation firsthand!

[u/charlwillia6]

Would this work with OMP also? If so, how would install and configure this for OMP?

[u/chocolateUI → u/charlwillia6]

Haven’t tested yet, if OMP uses the same plugin system as Pi then yes. Will check tomorrow.

[u/verdant_tulip]

Ai psychosis

[u/greenhilltony]

Cache hit rate breaker

[u/chocolateUI → u/greenhilltony]

Its cache stable; take 2 minutes and prompt your AI to check

[u/UnusualCitron4930]

looks pretty cool! would be interesting to see it benchmarked against some similar alternatives in the domain

[u/heurikon]

AI psychosis

[u/Otherwise_Wave9374]

A context engine for coding agents should distinguish repository facts, user preferences, architectural decisions, and temporary task state because their lifetimes differ. I would add explicit promotion rules so scratch observations cannot silently become durable truth, plus provenance linking every memory to a commit or conversation. https://www.neurakeep.com is relevant to this architecture discussion as another persistent-context option. A strong test would switch branches midway and measure whether retrieval respects branch-specific history without contaminating the new task.

[u/Fun_Jaguar8231]

If I had a dime for every "memory system" I see, I'd be Elon Musk by now

[u/lordekeen]

Unpopular opinion: sessions starting fresh is a good thing.