Bring Atomic Object's Agentic Engineering process into your repository.
Rhizome gives your team shared skills for defining work, planning implementation, building, and reviewing with AI agents. Specs, decisions, and delivery records live alongside your code, so the next developer or agent can pick up the context.
Setup installs the Agentic Engineering workflow by default. It gives your team defaults to adapt: how much planning a task needs, which checks prove it works, and when a person needs to make a decision. Small fixes stay small. The process guide explains how the team works together.
You'll need:
- A Mac with Apple silicon, or Ubuntu 24.04 with GNOME.
- A Git repository.
- Claude Code or Codex, installed and signed in on your computer.
- Node.js, available to your agent. Agents use it to run Rhizome scripts.
You don't need any API keys to begin.
Joining a repository that already uses Rhizome? Do step 1, then join the project.
On a Mac with Homebrew:
brew install --cask atomicobject/tap/rhizome-desktopThen open Rhizome from Applications. Homebrew also puts the app's rzm command on your PATH, which is how your coding agent reaches Rhizome. If you have the older CLI-only formula, run brew uninstall --formula atomicobject/tap/rhizome first.
Ubuntu, or a Mac without Homebrew
On a Mac, download Rhizome-macos-arm64.dmg, drag Rhizome to Applications, and open it.
On Ubuntu, download the x64 or Arm64 AppImage, move it somewhere permanent such as ~/Applications/Rhizome.AppImage, make it executable, and open it. Linux details
Then open Settings and, under Command-line tool, choose Install Command-Line Tool. This puts rzm on your PATH. macOS asks for an administrator password when it needs one.
The app updates itself. For Intel Macs, Windows, or a server, see the command-line installation. You can also ask your coding agent to install Rhizome for you.
Repository files update separately. Choose Update Rhizome files in the app to review pending changes. From the command line, use rzm init --check --json to preview them, then rzm init --take <path> or rzm init --keep <path> to resolve a file choice. Pass the preview's writes.decisionSnapshot as --decision-snapshot <token> to reject choices if the reviewed files change. Updating repository files
Choose Add Repository… and pick your repository's folder. Rhizome inspects it and shows what it found and every file setup would write. Nothing is written until you confirm.
The defaults suit most projects: the Agentic Engineering workflow, guidance for the coding agents Rhizome finds, and keyword search. Semantic search needs a Voyage AI key, which you can paste now or add later.
Choose Set up Rhizome. When it finishes, commit the files it lists so your teammates get the same setup, then choose Open workspace. What each choice means
If the repository already uses Rhizome, the app asks Trust this worktree? instead of showing setup. A worktree is your checkout of the repository. Choose Trust and open. Joining a project
Setup wrote AGENTS.md and agent skills into the repository, plus CLAUDE.md for Claude Code. Your agent reads them and runs rzm to search the project, read its notes, and check its changes.
Close any agent session already open in the repository and start a new one, so the agent finds the new skills. Or use the Agent tab in the app, which runs Claude Code or Codex in the repository for you.
Ask:
Use the rhizome skill to orient me to this repository. Show me the available workflow and any setup gaps before we start work.
The agent should describe the Agentic Engineering workflow. If it can't find rzm, or Codex can't reach Rhizome, see Make Rhizome available to your agent.
To shape new work:
Use the agentic-engineering skill to help me add password reset. Start with the intended behavior and the decisions we need to make.
For a clear fix:
Use agentic-engineering implement to fix this bug, verify it, and prepare a pull request.
The skill sizes the work and follows your team's policy. Before you delegate implementation, put your real test commands in docs/engineering/quality-gates.md, because the skills run them to prove work is done. Using the skills
Each window shows one repository. Three tabs matter at first:
- Notes shows the project's Markdown and the Delivery view, which tracks specs, stories, and efforts from shaping to done. On any piece of work, Copy workflow prompt copies the prompt that continues it. Paste it into your agent.
- Agent runs Claude Code or Codex in the repository.
- Tasks lists scheduled agent work that needs you.
Press ⌘K to search the project and ? to see every shortcut. A tour of the app
The setup gives you starting points to change. Edit docs/engineering/ with your team's test commands, review expectations, and release steps; the skills consult those documents as they work. Change workflows and add-ons from the repository's tab in Settings. As you learn, improve the skills or ask an agent to build views for your project. Adapting Rhizome
| You want to… | Read |
|---|---|
| Install on Linux, join a project, connect an agent, or set up search keys | Getting started |
| Define work, implement a spec, or capture meeting context | Using the skills |
| Change team policy, skills, data, or views | Adapting Rhizome |
| Build an experience: several views that run as one site, like Delivery | Build an experience |
| Schedule recurring agent work | Scheduled tasks |
| Let Rhizome learn from your agent sessions | Compounding |
| Browse and edit an existing AO KB's knowledge | AO KB knowledge |
| Compare workflows | Choosing a starter |
| Understand retrieval and links between notes and code | How Rhizome works |
Use rzm from a terminal or script, or install without the app |
Command-line reference |
| Diagnose slow indexing, runtime failures, or workspace stalls | Operational diagnostics |
| Contribute to Rhizome itself | Contributor guide |
Tell your agent: "Install Rhizome Desktop by following the 'Install with a coding agent' section of https://github.com/atomicobject/rhizome."
Agent instructions
These steps are for macOS with Apple silicon.
Prefer the desktop cask when Homebrew is available. If the CLI-only rhizome formula is installed, uninstall it first with brew uninstall --formula atomicobject/tap/rhizome. Install atomicobject/tap/rhizome-desktop with --cask, open the app, and verify command -v rzm, its symbolic link into Rhizome.app, and the app and CLI versions. Homebrew manages this CLI link, so skip the app's Install Command-Line Tool step. Preserve unrelated executables and report any collision instead of forcing an overwrite.
Use the following steps for a direct DMG installation when Homebrew is unavailable:
-
Stop and tell the user if
uname -mis notarm64; follow the command-line installation instead. If/Applications/Rhizome.appalready exists, skip to step 3, because the app updates itself. -
Download the notarized app, check it against the release checksums, and copy it into Applications.
set -euo pipefail base=https://github.com/atomicobject/rhizome/releases/latest/download tmp=$(mktemp -d) curl -fsSL -o "$tmp/Rhizome-macos-arm64.dmg" "$base/Rhizome-macos-arm64.dmg" curl -fsSL -o "$tmp/checksums.txt" "$base/checksums.txt" (cd "$tmp" && grep ' Rhizome-macos-arm64.dmg$' checksums.txt | shasum -a 256 -c -) mkdir "$tmp/mnt" hdiutil attach -nobrowse -readonly -mountpoint "$tmp/mnt" "$tmp/Rhizome-macos-arm64.dmg" ditto "$tmp/mnt/Rhizome.app" /Applications/Rhizome.app hdiutil detach "$tmp/mnt" open -a /Applications/Rhizome.app
-
Ask the user to open Rhizome › Settings and choose Install Command-Line Tool, and to enter their password when macOS asks. Wait for them to confirm. This is the only step that needs them.
-
Verify in a new login shell. The path should be
/usr/local/bin/rzmand the version should match the app's:zsh -lc 'command -v rzm && rzm --version' defaults read /Applications/Rhizome.app/Contents/Info.plist CFBundleShortVersionString
If another path comes first, Settings names it. Tell the user, for example to run
brew uninstall --formula atomicobject/tap/rhizomefor the CLI-only formula. -
Report the installed version. Tell the user to set up a repository by choosing Add Repository… in the app.
Rhizome is maintained by Atomic Object. Report a bug or suggest an improvement, or read the contributor guide. For vulnerabilities, follow the security policy.
Rhizome began as a fork of Yakitrak/obsidian-cli by Kartikay Jainwal. Thank you to the original author and contributors.
Rhizome is MIT licensed. Included third-party components retain their own licenses; see third-party notices.