AI memory for
developers.
Stop maintaining four CLAUDE.md,
CURSOR.md and GEMINI.md files.
One persona, every editor and CLI, every machine.
One file, not four
Your conventions, the way you like reviews, the things the assistant should refuse — held once. Edit it in one place and every tool updates. No more four versions of the same instructions drifting apart.
13 editors over MCP
Claude Code, Cursor, VS Code, Windsurf, Zed, JetBrains AI, Continue.dev, Cline, Aider, Augment, Antigravity and Gemini CLI — wired through MCP and rules files. Plus 21 cloud chat surfaces in the browser.
Import what you already have
Point aiperson at the CLAUDE.md and CURSOR.md files you already keep. They fold into one persona — conventions and refusals you can read, edit and version, not scatter.
Every machine you code on
The persona is a git-backed file, so it follows you to laptop, desktop, work and personal. Sign in, run two commands, and a new machine inherits everything your assistant already knows.
Local-first, signed, yours
Persona signed with a key generated on your machine; corpus in a local SQLite file. Nothing hosted by default. Export the whole thing any time — leaving is a feature, not a fight.
Frequently asked questions
What is an AI memory for developers?
An AI memory for developers is a single persona — your conventions, the way you like code reviewed, the things your assistant should refuse — held in a file you own and read by every editor and CLI you use. Instead of maintaining a separate CLAUDE.md, CURSOR.md, GEMINI.md and AGENTS.md, you cultivate one persona and aiperson projects it into 13 editors and CLIs over MCP.
Which editors and CLIs does it support?
Thirteen over MCP and rules files: Claude Code, Cursor, VS Code (Copilot), Windsurf, Zed, JetBrains AI, Continue.dev, Cline, Aider, Augment, Antigravity and Gemini CLI. It also reaches 21 cloud chat surfaces through the browser extension, so the same persona is present when you ask ChatGPT, Claude or Gemini in the browser too.
Can I import my existing CLAUDE.md and CURSOR.md files?
Yes. You point aiperson at the instruction files you already maintain and it folds them into one persona — your conventions and refusals become first-class values you can read, edit and version, rather than four drifting copies of the same rules.
Where does my persona live?
In a signed file in a git repo you own, with your corpus in a local SQLite database on your machine. Nothing is hosted by default. You decide, per data kind, what (if anything) is mirrored for cross-device sync — and you can export the whole thing any time.
Does it work across multiple machines?
Yes. Because the persona is a git-backed file, it follows you to every machine you sign in on — laptop, desktop, work and personal — and a daemon reconciles changes roughly every five minutes so your editors stay in step.
Cultivate one AI. Keep it yours.
One persona across every editor, CLI and machine. Free while we build toward our first 100 Founding Members.