MindrianOS ships as a Claude Code plugin and can be installed three ways: the npm one-liner (recommended for most users), the Claude plugin marketplace directly, or a shell script for manual and dev-clone installs. All three paths produce the same result — the same Larry, the same room, the same hooks on session start.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/jsagir/mindrian-os-plugin/llms.txt
Use this file to discover all available pages before exploring further.
MindrianOS requires a paid Claude plan. Claude Pro ($20/mo) is the minimum. The free tier does not support the extended context and tool-use capabilities that MindrianOS depends on.
Requirements
- Node.js ≥ 22.5.0 — check with
node --version. Theenginesfield in the package enforces this floor. - Claude Code CLI on PATH — the installer drives Claude Code’s own plugin system. Run
claude --versionto confirm it is available. If it is missing, install it withnpm install -g @anthropic-ai/claude-code.
Install
- npm (recommended)
- Plugin marketplace
- Shell script
The npm package is the verb: running it with no subcommand performs the install. This is the recommended path for all new installs.What the installer does, in order:When a version is pinned, the update step is skipped so the plugin stays at the version you specified.
- Confirms the
claudeCLI is on your PATH - Registers the Mindrian plugin marketplace (
jsagir/mindrian-marketplace) - Refreshes the marketplace catalog so the current release resolves
- Runs
claude plugin install mos@mindrian-marketplace - Runs
claude plugin update mos@mindrian-marketplaceto bring the plugin to the latest build
--version:First launch
After install, restart Claude Code completely before opening a session. The hooks that load your room context and activate Larry fire on session start (SessionStart hook) — they will not activate in a session that was open during install.
On first launch, Claude Code may present permission prompts for the shell commands that MindrianOS uses during session setup. 10 or more prompts is normal. For any command you are comfortable with, choose “Always allow” — that permission will not re-prompt again. For zero prompts on every subsequent session, you can start Claude Code with:
~/MindrianRooms/. For granular control without skipping all permissions, copy the matcher set from docs/settings-template.json in the plugin repo into ~/.claude/settings.json.
Update
mindrian-os update refreshes the catalog and runs claude plugin update. For a dev clone (where MINDRIAN_OS_ROOT is set or a .git directory is detected), it runs git pull --ff-only followed by bash install.sh in the install directory.
Repair and diagnostics
Run the diagnostics CLI outside of Claude Code to catch install drift before a session:/mos:doctor uses inside Claude Code. It checks commands, skills, agents, hooks, the statusline block, and (optionally) the Brain connection. If MindrianOS is not installed, it says so plainly instead of throwing a stack trace.
You can also run diagnostics from inside a Claude Code session:
Advanced configuration
MINDRIAN_OS_ROOT environment variable
For dev clones or non-standard install paths, set MINDRIAN_OS_ROOT to the absolute path of your MindrianOS directory. The CLI and the plugin both read from this variable first. When it is set, mindrian-os update uses the git-pull path instead of the marketplace path.
/mos:setup inside a session and choose “Configure Brain.”
claude --dangerously-skip-permissions
For a zero-prompt session experience, start Claude Code with this flag. The plugin’s read/write surface is bounded to your workspace and ~/MindrianRooms/, so the risk surface is well-defined.
Troubleshooting
If commands are not recognized or the plugin appears missing after install, the most common fix is a full reinstall:mindrian-os doctor --all and check the output for the specific failing step.