Where humans and agentsThink from shared understanding.

MindMux compiles the background, decisions, and constraints from your discussions into a project brain, so shared understanding accumulates and work keeps moving forward.

MindMux chat screenshotMindMux brain screenshotMindMux task screenshot
Works with
Claude Claude CodeOpenAI CodexGithubCopilot GitHub Copilot
and more.

How it works

Think → Compile → Build, project context stays with the work the whole way through.

01 · Think
chat — auth flow
02 · Compile
brain/pages/auth-strategy.md
Compiling…
status: active · category: decision
source: this chat
03 · Build
task — dispatch
Waiting for a decision to compile…

Every decision lands as plain Markdown — searchable, diffable, and readable by the next agent (or the next you). Ready ones dispatch straight to execution.

Before and after

Three everyday moments, watch what changes when nothing gets lost between sessions.

01

Stop re-explaining yourself

Before
You ❯Let's keep working on the auth flowAI ✦Sure — what's the app? Stack? What are you building? Any constraints? Team size? Timeline?You ❯[612 words re-explaining the project. Again.]— Sixth time this week.
AfterFive words in, and it already knows.
You ❯Let's keep working on the auth flowAI ✦Reading brain/index.mdPicking up from last time:· Electron + SQLite, local-first, single user· JWT ruled out — no server, not worth it· Still open: session persistenceWhere do you want to start?
02

Decisions that stay put

Before
You ❯JWT vs session tokenAI ✦Searched 214 conversations, three Slack threads, and a Notion page for “JWT decision.”— It's in there. Somewhere. Maybe.
AfterDecided once. Still here.
You ❯JWT vs session tokenAI ✦Reading brain/pages/auth-strategy.mdConclusion: Cookie-based sessionsWhy: No server → JWT adds overhead. SQLite session store fits the local-first constraint.Decided 3 weeks ago
03

Your context goes with the task

Before
You ❯Implement OAuth callbackPasted 1,400 words of project context — twice, because the first paste got cut off — before Claude Code could start.— Forty minutes. Just to re-brief the agent.
AfterThe context goes with it. You don't.
You ❯Implement OAuth callbackAI ✦Stack: Next.js + Prisma + PostgreSQLAuth: GitHub OAuth via next-authConstraint: No breaking DB migrationIncludes 12 brain pages · auto-attached

Features

The pieces behind think, compile, and build.

Markdown Brain

Your durable output lives in plain files under brain/, readable by humans, git, and external agents.

Compiled Truth + Timeline

Separate the current best understanding from the observations and decisions that led there.

Root Docs

Keep background, architecture, flow, mindmap, stack, and roadmap as stable project documents.

Local-first

Project memory stays on disk. Runtime choice is separate from the brain you are building.

Expert Modes

Switch between product, CTO, architect, researcher, and handoff thinking without binding roles to one model.

Task Handoff

Turn discussion into structured tasks for coding agents or GitHub issues, with context attached.

Why not other tools?

Existing tools either forget the conversation, skip the reasoning, or make you do the writing. MindMux closes the loop.

ToolWhat happens to the thinkingWhat's left
ChatGPT / Claudegeneral-purpose chatGreat conversation — then it's over. The chat ends and the reasoning scrolls away.A chat log nobody re-reads
Cursor / CopilotAI coding assistantsThey write the code, but not why. The trade-offs behind the diff live nowhere.Code without its rationale
Notion / Obsidiannote-taking toolsSolid storage — but you do the writing. Notes happen only when you stop to take them.A blank page and a chore
MindMuxthink → compile → buildThe discussion is the work. It compiles into decision artifacts automatically, then dispatches to execution agents.A living, portable brain

FAQ

Which AI models can I use with MindMux?

MindMux is model-agnostic. Because memory is plain Markdown, you can work with Claude, GPT, Codex, and future models without migration.

Where is project memory stored?

On your Mac, in a folder you control. MindMux writes Markdown files to brain/ inside your project directory. No forced cloud sync and no account required.

Can I adopt MindMux in an existing repo?

Yes. Point MindMux at any directory and it creates a brain/ folder alongside your existing codebase.

How is this different from Obsidian or Notion?

MindMux is built for the AI execution loop. It helps you think, compile, and build with shared context, not just store notes.

Is MindMux open source?

Yes. The MindMux client source code is planned to be progressively published so you can read, fork, and self-host the code as it is released.

Turn your thinking into shipped work.

Keep project context intact from first question to final handoff. It all lives in a local Markdown folder that's yours — git it, move it, read it with any tool.

Download MindMux