Skip to main content
MindrianOS
MindrianOS· in beta

Most people solve
the wrong problem first.

MindrianOS turns Claude into Larry, a thinking partner built from 20 years of teaching people how to find problems worth solving. Tell him where you are stuck. He brings the right method at the right moment, fits it to your situation, and writes every decision into a room that remembers.

And when he does not know, he says so, plainly, and files the gap. No guessing dressed up as teaching.

One command installs it. The Brain is part of what installs.
$ npx @mindrian_os/cli

Free plugin, in beta. Requires a paid Claude plan (Claude Pro, $20/mo, or higher). See pricing.

ask-larry - live12 ON THE HOUSE
Ask Larry anything. This is the real thing, not a script.

The real Larry, not a script. Free Brain-grounded answers for a few tries, then keep chatting or grab your own key at /brain-access.

The loop

The whole product, drawn as one loop.

Every conversation with Larry makes this exact trip. Watch it go around: each turn ends with the room knowing more than it started with.

1you

You say where you are stuck.

A stalled project, a half-formed idea, a claim you cannot defend yet. Plain words are enough.

2the Brain

The graph answers.

A live map of 181 thinking methods, built from 20 years of real teaching, picks the one that fits this exact moment.

3Larry

Larry makes it yours.

He does not recite the method. He applies it to your situation and pushes back where the reasoning is thin.

4you

You decide what sticks.

Keep it, reject it, or park it. Even a rejection is saved, with the reason.

5the room

The room writes it down.

The next session starts where this one ended. You never re-explain.

Honesty

When it does not know, it says so.

Two rules keep Larry honest. Every method answer names its source in the graph. And when the graph has nothing, Larry refuses instead of improvising, then queues the gap so a future release can answer for real. Watch him do both:

claude code - larry, on the record
>My users churn after week two. Where do I start?
$Start with the forces, not the churn number. People switch when the push of the problem beats the pull of the product. Map both before you touch a feature.
source: BRAIN · jobs-to-be-done, the forces of progress
>What does the method say about pricing a DAO token?
$Nothing yet, honestly. The Brain has no grounded method for token design, and I will not dress a guess up as teaching. I have queued the gap; when it enters the graph, you will get a real answer.

That refusal is not a failure state. It is the point: if Larry cannot cite the teaching, he does not pretend to teach.

Get started

One command. The Brain comes with it.

No terminal experience needed. The Brain, the map Larry teaches from, installs and connects on its own. Already have a key? Yours wins.

1

Run one command

Paste this into Claude Code and press enter.

npx @mindrian_os/cli
2

Approve the prompts

Claude asks before it touches anything. About ten prompts the first time is normal, not a problem. Pick “always allow” on the ones you trust.

3

Start talking

Larry wakes up, the Brain connects, and the room starts taking shape underneath the conversation.

Brain APIFree 30-day trial
Your work stays yours

One graph teaches. One graph is yours.

Think of a teacher and your notebook. The teacher (the Brain) knows the method and writes into your notebook. The notebook (your room) never leaves your desk, and nothing you write in it is ever copied into the shared map. A pattern from one of your projects can light up in another, without your files changing hands.

How the Brain works
The dual graph
One graph teaches the method. One is your private notebook. The teacher writes into yours; your files never leave your desk.
Who uses it

Anyone working a hard problem across weeks.

Researchers

Arrive with a hypothesis, use it to validate and stress-test toward rigorous analysis.

Founders

Arrive with a direction but no destination, use it to find the real problem and build.

Innovation courses

Students explore unfamiliar domains and build opportunity portfolios across a term.

Tech transfer

Triage large portfolios of disclosures, frame problems, and test commercial viability fast.

Deep-tech ventures

Competitive positioning and strategic paths, with claims checked against the record.

Creative and corporate

Product lines, curricula, procurement, and regulatory work that span many sessions.

The team

Who built this.

The methodology

Problems Worth Solving (PWS)

Two decades of teaching innovation, developed through direct application with students, startups, corporations, and government: the codified, tested practice MindrianOS runs on.

The build

Jonathan Sagir

Co-founder and builder. Architected MindrianOS: the persistent Data Room, the methodology engine, the knowledge graph, the proactive intelligence layer, and the deployment infrastructure.

More about the project
Ready

Start the loop.

$ npx @mindrian_os/cli

v2.0.0-beta.1 “Build the Loop” · the release that taught Larry to say “I don't know”