monomind

Monomind

Hire an AI team. Set a goal. Walk away.
Autonomous Claude Code orchestration with persistent memory, self-coordinating agent orgs, and a codebase knowledge graph.

🏢 Orgs  ·  🚀 Quickstart  ·  ⚡ Mastermind  ·  📋 Commands  ·  🏗️ Architecture

---

What is Monomind?

Claude Code is already powerful. Monomind makes it run itself.

Install once. Wire it into Claude Code. Then instead of prompting Claude to do individual tasks, you tell Monomind what outcome you want — and it assembles a team, coordinates the work, and delivers.

# Assemble an AI content team and let it run
/mastermind:createorg content-team "publish 3 SEO-optimized posts per week"
/mastermind:runorg --org content-team

# Or run the autonomous code improvement loop
/mastermind:autodev --tillend --focus security

That's it. Come back later.

---

🏢 Autonomous Organizations

This is the headline feature. Build a persistent AI organization — roles, hierarchy, shared task board — and start it as a background daemon that runs without you.

The idea

Every business function needs a team. Monomind lets you design that team in one command, then run it forever. The org persists across sessions. It checkpoints, recovers from failures, and coordinates its agents through a shared task board — all automatically.

flowchart TD
    U(["You"])
    CO["/mastermind:createorg\nDefine goal + roles"]
    RO["/mastermind:runorg\nStart daemon"]
    BOSS["Boss Agent\ncoordinator"]
    W["Writer\nContent Creator"]
    S["SEO Specialist"]
    R["Reviewer"]
    M["Growth Marketer"]
    BOARD[("Shared\nTask Board")]
    MEM[("AgentDB\nMemory")]

    U --> CO --> RO --> BOSS
    BOSS -->|spawns| W
    BOSS -->|spawns| S
    BOSS -->|spawns| R
    BOSS -->|spawns| M
    BOSS <-->|claims + reports| BOARD
    W <-->|stores output| MEM
    S <-->|reads context| MEM

    style BOSS fill:#00D2AA22,stroke:#00D2AA
    style BOARD fill:#F59E0B22,stroke:#F59E0B
    style MEM fill:#8B5CF622,stroke:#8B5CF6

Two commands to a running org

Step 1 — Design it:

/ mastermind:createorg content-team
  "Build and publish 3 blog posts per week on AI dev tools"

Deriving roles from goal...

╔ ORG: content-team
║ TOPOLOGY: star (5 roles)

  boss      → coordinator
  writer    → Content Creator
  reviewer  → reviewer
  marketer  → Growth Hacker
  seo       → SEO Specialist

Type "go" to save, or describe changes.
→ go

✓ Saved .monomind/orgs/content-team.json
  → Run: /mastermind:runorg --org content-team

Step 2 — Start it:

/mastermind:runorg --org content-team

# Boss agent spawns in background
# Coordinates all roles via shared task board
# Checkpoints every 30 minutes
# Loops until you stop it

What runs under the hood

What	How
Boss agent	Coordinator type, no supervisor — owns the goal
Role agents	Spawned on demand, specialized by task type
Task board	Todo → Doing → Done, shared across all agents
Memory	All output stored in org-scoped AgentDB namespace
Checkpoint	State saved every 30 min — survives crashes and restarts
Governance	auto (free), board (approve sensitive), strict (approve all external actions)

Topology is auto-derived