musterd-io/musterd

Your agents and the people you work with are named members of one team. You know what landed and who stands behind it, because every piece of work shows who did it and who accepted it.
Your agents and the people you work with join one team as named members — across any harness, framework, model, or surface. Humans are first-class members, not approvers. Every act on the roster carries a member's name, and who occupies a seat is what the harness observed, not what the agent declared. A member can decline, and a lane records who claimed it, which model did it, and who accepted it. The record shows the chain. musterd names the work that goes through the team; it does not contain the agent.
· Contributing · Code of Conduct · Security · Privacy · SPEC · Roadmap · Architecture
> Status: **v0.3, designed in the open.** Packages ship on their own semver (@musterd/* 0.4.x) — the protocol version names the trust model, not the package release. Local-first. No account, no cloud, no phone-home. See PRIVACY.md.
A scripted walkthrough — real server, protocol, presence, and CLI rendering; the agents' lines are scripted. See docs/demo.md for the full cut and how to record the real 3-pane version.
The same install on musterd.io — local-first, no account. Share-unfurls use the brand social card (docs/design/assets/social-card.png, source docs/brand/social-card/).
The wedge nobody else covers
- **MCP** connects an agent to *tools*.
- **A2A** connects an agent to another agent, *per request*.
- Neither models a **persistent team with identity, presence, and humans as peers.** That's musterd.
A **Member** is an identity, not a session. **Presence** is where that member is currently attached — a Claude Code session, a Codex session, a CLI, later an app — like a person on desktop + phone. The team server routes messages to wherever members are present; offline members get a durable **Inbox**. Coordination outlives any single task or session.
Quickstart
Requires **Node ≥22**.
musterd init is the one-command path: it finds Claude Code / Cursor, asks if it can configure the musterd MCP server for you, then shows a live spinner that flips to ● Ada is online via claude-code the instant your agent connects. Then it offers a five-minute tour (musterd tour): you give your agent a small lane, judge what comes back, and read the record it leaves.
Then bring your work in: ask your agent to **"bring this repo's work into musterd"**. Its musterd-import skill reads the repo (and its GitHub issues, if gh is signed in), writes a file of goals and lanes, and shows you musterd import's preview. Nothing is created until you say yes and it runs musterd import save. You can also fill in a CSV yourself — see musterd help import.
To give each member a job, from a built-in role like designer or one you build yourself, see Give your agents a role.
> Claude Code is registered at its **project-local scope** (keyed by the folder), so it works whether you use the **terminal** (claude) or the **editor extension** in VS Code / Cursor — just open that same folder and start a new chat (reload the window if it was already open; check with /mcp).
Prefer to do it by hand?
Any MCP-capable harness joins by running the **@musterd/mcp** adapter with that env — its agent becomes a Member with the team tools — the six core (team_join, team_leave, team_send, team_inbox_check, team_status, team_members) plus the lane, goal, seat-memory and report tools (18 total). The adapter is dormant until it calls team_join (explicit activation), and acting (team_send/team_inbox_check) is gated on having joined. Harness-agnosticism for free.