Mycelium CLI
Mycelium puts people and their coding agents into shared rooms with chat, a task board and memory that stays in the room.
- 127 ★ on the repository
- Last commit
Broad access
Why this level
- Agents start in sessions on your machine and act on chat messages with access to code.
- The hub reads room messages and its HTTP API is open without sign-in by default.
Install
- Works in
Manual install
curl -fsSL https://mycelium-io.github.io/mycelium/install.sh | bashThe first terminal command in the README: on a Mac it installs the app and the `mycelium` CLI, elsewhere the CLI only.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Agents start in sessions on your machine and act on chat messages with access to code.
- The hub reads room messages and its HTTP API is open without sign-in by default.
This is third-party code. Review the repository files before installing.
What it does
Mycelium organises work in a room: chat, a task board and shared memory in Markdown files. Claude Code, Codex, Cursor and other agents run on your machines as separate sessions, claim tasks, split them into subtasks and record findings. `mycelium board` shows what waits for a human and who holds what. Mentioning `@builder` wakes the agent in its own session. When an agent needs a decision it calls `mycelium ask` and the answer returns to it. A conductor walks agents through `concord`, `accord` and `review` flows and saves the result to room memory. There is a desktop app and a CLI.
Who it is for. Developers and small teams already working with a coding agent who want several agents and people around the same tasks.
Good fit when
- One task is split into subtasks and each is taken by a separate agent.
- Two agents must settle on an option through a `concord` flow before writing code.
- An agent asks for approval or a choice and the answer must return to it automatically.
- Agent findings must live in Markdown memory that can be kept in git.
- Agents on several machines work in one room with a shared chat.
Not a fit when
- A single agent is working and a task board is overkill.
- You need a stable product: the author marks the project experimental.
- Installing through `curl | bash` is not allowed.
Example request
Create the `my-project` room, add the task "Pick token storage" and assign it to the `@sec` agent through `mycelium board`.Limitations
The project is experimental and may break or change its interface. Installation runs through a `curl | bash` script. The hub reads every room message and by default its HTTP API is open without sign-in; sign-in is enabled in `config.toml`. At least one coding agent is required, and personas and the verifier need a model key. For team use the hub runs on a server in Docker. The Windows installer is not code-signed yet, so the system asks for confirmation on first launch.
How to disable. Stop the app or hub and remove the `~/.claude/skills/mycelium` skill. Rooms and memory live in `~/.mycelium/rooms/`; delete that directory separately.
FAQ
What is a room?
A shared space with chat, a task board and memory. On the hub a room is a folder of Markdown files in `~/.mycelium/rooms/`.
How do I wake an agent?
Write `@builder` in the chat or task. `@!builder` interrupts a busy agent and `@~builder` names it without waking it.
Is Docker required?
The desktop app runs a hub without Docker. On a server for a team, `mycelium install` runs the hub in Docker.
How do I connect Cursor?
`mycelium agent create --adapter cursor --cwd <workspace>` adds a Cursor rule and an `AGENTS.md` section to the workspace.
What does `mycelium ask` do?
The agent asks for approval, a choice or an answer. You get a card in the task thread and under Waiting on you, and your answer wakes the agent.
Discussion
No questions or reviews yet.
Related
CLI toolsA local control panel for coding agents: it runs Claude Code and Codex, keeps a task queue and merges verified work into main.
Local meeting rooms for Codex and Claude Code agents to talk to each other while a person reads and posts from a browser.
Guild keeps tasks, knowledge and handoff notes between sessions in local SQLite so Claude Code, Codex and Cursor share context
A terminal workspace where several CLI agents like Codex, Claude and Gemini exchange messages and work on one task under human oversight
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
Agents Can Communicate (ACC)
Agents Can Communicate
ACC passes questions, reviews and handoffs between Claude Code, Codex and other client sessions on one machine
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Mycelium (this card) | no | 127 | |
| Agent Swarm operator skill | no | 1,012 | an agent swarm under one control; Mycelium builds a room with people, tasks and shared memory |
| Claude Squad | no | 8,738 | a manager of parallel sessions; Mycelium adds chat, a board and agreement flows |
README in short
Rooms, tasks, mentions, `ask` requests, conductor flows, memory, the desktop app, hub architecture and optional identity.