Skip to main content

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 installs in a single command and activates the moment you restart Claude Code. There is no configuration wizard, no workspace setup, and no framework to learn. You install, you restart, you talk — Larry handles the rest.

​
Prerequisites

Before you install, confirm the following:
  • Node.js ≥ 22.5.0 — check with node --version. Download from nodejs.org if needed.
  • Claude Code installed — the claude CLI must be on your PATH. Run claude --version to confirm.
  • Paid Claude plan — Claude Pro ($20/mo) or higher. MindrianOS runs on top of Claude and requires a plan that supports extended context and tool use.
Not sure which Claude plan you have? Visit claude.ai/settings to check. The free tier is not sufficient — MindrianOS relies on Claude’s tool-use and extended context capabilities.

​
Install MindrianOS

1

Run the one-line installer

Open your terminal and run:
npx @mindrian_os/cli
This registers the Mindrian plugin marketplace, refreshes the catalog, and runs claude plugin install followed by claude plugin update to bring the plugin to the current build.
2

Approve the Claude Code permission prompts

Claude Code asks you to approve each shell command it runs during install. 10 or more prompts is completely normal. For any prompt you are comfortable with, choose “Always allow” — that permission will not re-prompt for the rest of the session or future sessions.
Choosing “Always allow” on the first few prompts dramatically speeds up subsequent sessions. The read/write surface is bounded to your workspace and your rooms at ~/MindrianRooms/.
3

Restart Claude Code

Once the installer finishes, fully close and reopen Claude Code. The hooks that load your room context and activate Larry fire on session start — they will not run in a session that was already open during install.
4

Verify the install (optional)

Run the diagnostics CLI to confirm everything is wired correctly:
mindrian-os doctor --all
You can also run /mos:doctor from inside a Claude Code session.

​
Start your first room

There is no setup command to run and no project to initialize. Just open a Claude Code session and start talking. Describe what you are working on in plain language: 
I'm working on a marketplace that connects independent contractors 
with small businesses for short-term projects. The problem I keep 
running into is that contractors don't trust the platform enough 
to lower their rates, even when jobs are guaranteed.
Larry will respond by reframing the problem, asking clarifying questions, and beginning to build the room around your conversation. You do not need to know any framework names or command syntax. Alternatively, type /mos:ignite as the explicit front door if you prefer a structured onboarding sequence. Larry will guide you through naming your room, describing the venture, and opening the first discovery session.

​
What a first Larry conversation looks like

Larry does not mirror your framing back to you. It probes before it proposes:
Larry: Before we work on the trust problem, I want to make sure we’re solving the right one. A few things: When you say contractors “don’t trust the platform,” have you confirmed that with actual contractors — or is this an inference from low adoption? Those point to very different fixes. Also: is the rate discount a feature you’re offering, or something contractors are doing on their own when they win a guaranteed job? I’m asking because the constraint might not be trust at all — it might be that the value proposition for the discount isn’t legible to contractors yet. What do the conversations with your first 10 contractors look like?
This is the pattern Larry returns to throughout: reframe the problem, surface the assumption, ask for the evidence. The room fills as you answer.

​
What gets created

After your first session, MindrianOS will have created a room folder at: 
~/MindrianRooms/<your-room-name>/
The folder structure organizes itself by venture stage — problem, market, solution, team, financials, IP, meetings, and opportunities. You own this folder entirely. Nothing is synced anywhere. Back it up like any other directory.
The MINDRIAN_OS_ROOT environment variable overrides the default install location. This is primarily useful for development clones — most users should leave it unset.

​
Next steps

Your First Session

A deeper walkthrough of what to expect in a first Larry session and how to get the most from it.

Meet Larry

How Larry thinks, what it does on your behalf, and why the pushback is the point.

Command Reference

All 111 /mos: commands — what they do and when Larry reaches for them.

Installation Options

Marketplace, npm, and shell install paths. Update, repair, and version pinning.

Build docs developers (and LLMs) love

Get started for freeTalk to us