Skip to content

Coming from another harness

If you already use Claude Code, Hermes Agent, Cursor or Prime, a lot of what you know carries over. This page maps your habits onto Rhizome, and shows what’s different: memory lives in a folder you can read, and you can see where a run went.

In most harnesses, memory is a file or store that belongs to the tool: MEMORY.md, USER.md, a database, a cloud account. In Rhizome, memory is your vault, a folder of Markdown notes. You choose what’s saved with Save to vault. With Prime, answers that use a note say it came from your vault. With Git, every change can be diffed and reverted. See Your vault is the agent’s memory.

In Claude CodeIn Rhizome
Your past sessionsSettings → AI Agents → Import chat history brings them into the vault as notes under Imports/claude-code/. See Import Claude Code history
CLAUDE.mdThe vault’s AGENTS.md. Rhizome keeps a CLAUDE.md alongside it for compatibility
MCP serversRhizome is an MCP server too. Set Up External AI Tools… (⌘K) adds it to Claude Code’s config, so Claude Code can read and write your vault from the terminal
Claude modelsNot on Rhizome’s own engine yet; use another provider or Taproot
Permission promptsPermission modes, Limited tools and Power User, set per vault
/resumeThe sessions list. See Sessions

Rhizome doesn’t run Claude Code inside Chat. Keep using Claude Code in the terminal, connected to your vault through MCP.

In HermesIn Rhizome
MEMORY.md / USER.mdVault notes you save on purpose. Automatic saving exists but is off by default
Memory writes you approveSave to vault is an explicit click. It writes straight away, so review the note after, or undo with Git
Observable, interruptible runsStop any run; with Prime, send a follow-up while it works; see a Prime run’s file footprint in Mycelium
SkillsRhizome’s own plugin system is planned
Your choice of providerYour own providers, local models or Taproot. Keys live in the system keychain
In CursorIn Rhizome
Agent chat beside your filesChat with notes beside it (⌘2 shows Notes)
Cursor’s MCP settingsSet Up External AI Tools… (⌘K) writes Rhizome’s MCP entry into ~/.cursor/mcp.json, so Cursor’s agent can use your vault
Rules filesThe vault’s AGENTS.md
Model pickerYour providers or Taproot

Rhizome isn’t a code editor. Keep Cursor for code, and use Rhizome as the place where what you and your agents learn is kept, reviewed and found again.

Add a provider or use Taproot. Rhizome’s engine can read, search, edit, and create notes in the open vault. Power User can run one approved shell command in the vault folder. See Set up models and keys.

Rhizome’s own plugin system is planned, not shipped. Other apps can reach your vault through MCP.