Operator Memory
The self-improving context engine for coding agents.
Install
git clone https://github.com/aerovato/operator-memoryInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →English | 简体中文
Operator Memory: The self-improving context engine for coding agents.
Operator Memory gives your agent a brain for documenting all their work. As the agent works, it automatically documents within this brain — specs, decisions, standards, research, lessons. Every new session starts knowing everything the last one learned.
Features
- Complete Context Engine — Documentation, memory, indexes, and skills within a single integrated system.
- Automatic Documentation — Specs, decisions, research, and more are automatically documented by the agent.
- Transparent Memory — Memory is stored as Markdown documents you can read, update, and delete.
- Sharable Knowledge — Track documents with Git and share knowledge with your team.
- Zero Infrastructure — No background agents, no embeddings, no vector database, no model configuration.
Installation
Operator is managed via the Operator Helper, which also provides setup and agent instructions. Install the Helper with npm:
npm install --global @aerovato/operator-helper
Or Bun:
bun add --global --minimum-release-age 0 @aerovato/operator-helper@latest
Then install the Operator adapter for your harness. Click each link for harness-specific information.
| Harness | Status | Install |
|---|---|---|
| Claude Code (CLI + Desktop) | 🟢 Fully Supported | operator-helper install claude-code |
| Codex (CLI + Desktop) | 🟢 Fully Supported | operator-helper install codex |
| OpenCode V2 | 🟢 Fully Supported | operator-helper install opencode-v2 |
| OpenCode V1 | 🟡 Supported, Legacy | operator-helper install opencode |
| Pi | 🟢 Fully Supported | operator-helper install pi |
| DeepSeek Harness | 🟢 Fully Supported | operator-helper install deepseek |
| Kiro | 🟡 Supported | operator-helper install kiro |
Setup is a conversation with your agent. Run each command in a new conversation.
- First time only:
/operator:user-init— set up your global user partition. - In each new project:
/operator:project-init— scaffold Operator, migrate existing documents, and index the repo. - Start a new conversation and do normal work.
When starting cold on an existing project, expect a sparse brain at first; ask the agent to write the first specifications for the modules you work on. Once those documents exist, later sessions maintain them as part of ordinary work.
New to Operator? Read the Getting Started guide.
How Operator Works
Agents excel in a single session but forget everything the moment it ends. Future sessions waste tokens re-gathering an incomplete context: re-exploring the codebase, re-learning the architecture, re-teaching decisions and corrections.
Operator gives the agent a durable workspace of Markdown, kept in three places:
.operator/— private project knowledge, stays on your machine.operator-shared/— project knowledge published with the repository~/.operator/user/— your personal rules and knowledge, used across projects
Every session runs the same loop:
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
Production-grade engineering skills for AI coding agents.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…