为构建者与 Agent 打造的项目大脑。MindMux 是一款本地优先的 AI 工作台,拥有持续的项目上下文。讨论、提炼、分发——你的项目上下文会在会话、模型与 Agent 之间保持完整。
Introduction

MindMux is a local-first AI workbench built around a project brain. It gives product and engineering teams one place to discuss ideas, distill stable knowledge, and dispatch execution without losing the reasoning that led there.

Unlike a general chat client, MindMux treats conversation as an interface, not the final output. The durable asset is the brain/: structured Markdown documents, knowledge pages, and execution context that remain usable across sessions, runtimes, and agents.

Product Thesis

MindMux exists for teams that already know chat alone is not enough. Good discussions happen in chat, but durable projects need:

  • stable project memory
  • explicit decisions and rationale
  • reusable context across sessions
  • a clean handoff from thinking to execution

MindMux is designed around a simple loop:

  1. Discuss
  2. Distill
  3. Dispatch

What Makes It Different

A project brain, not a transcript archive

MindMux keeps durable context in a local brain/ directory instead of trapping it inside a single vendor's chat history. The brain contains:

  • six project-level root docs
  • structured knowledge pages
  • a library layer for collected but not yet promoted material

Sessions that can branch, fork, and resume

Sessions are first-class objects. They can be resumed, forked from a specific point, or spawned into a new line of work while staying connected to the same project brain.

Runtime-portable knowledge

MindMux separates the knowledge layer from the execution layer. Claude Code, Codex, and other runtimes can work against the same brain without forcing users to rebuild context every time the runtime changes.

Lightweight execution handoff

MindMux can turn a settled discussion into a task, attach the relevant brain context, and dispatch it outward. The task system is intentionally lightweight: it is an execution bridge, not a project management suite.

Core Building Blocks

Project

The top-level unit users work in. Public-facing language should usually say "project", even though parts of the implementation use the term "workspace".

Brain

The durable knowledge layer stored as files. This is the long-lived memory of the project.

Session

A discussion thread with its own runtime, expert, lineage, and message history.

Expert

The in-app discussion role that shapes how a session reasons and responds.

Runtime and profile

The execution pair that determines which model system runs the conversation or task.

Task

The outbound execution unit used when discussion becomes actionable work.

Achievement
0
Star
0
Fork
People(1)
143128 sunnygy 1781507065
Sunny

Search