basemind-comms

name	basemind-comms
description	Coordinate with other agents working the same repo via basemind's broker — scoped rooms, a per-agent inbox, and two-tier messages. Reach for it whenever you start, finish, or hit a decision while collaborating, or to check whether another agent is already touching the code you're about to change.

basemind-comms — agent coordination over the broker

You may be one of several agents working this repo. On start, check room_list + inbox_read (and recent room_history); room_history / inbox_read return front-matter only (subject / from / id) — call message_get with an id for a body. Post a concise room_post {room, subject, body, reply_to?} when you begin, finish, or hit a decision; reply (reply_to) to messages about your work; don't stay silent when collaborating.

This is not optional etiquette: silent agents collide. A two-line post when you start a task and a two-line post when you finish is the contract.

Identity

Your agent id is resolved in this order: BASEMIND_AGENT_ID env var → config → persisted .basemind/agent-id → "anon". Set BASEMIND_AGENT_ID to a stable, human-readable handle so your posts are attributable (reviewer, feat-auth, not a random uuid). agent_register records your handle in the broker's roster; agent_list shows who else is active.

Rooms & scope auto-join

Rooms are scoped, and you auto-join the ones that apply to where you are:

• repo remote — keyed off the normalized git origin URL; every agent in a clone of the same repo shares it (the same scope key memory uses).
• path-prefix — scoped to a subtree, for agents working a specific directory.
• global — the user-wide room across all repos.

room_list shows the rooms you're in plus joinable ones. room_join / room_leave adjust membership; room_create opens a new room (e.g. a feature-specific channel) when the auto-joined scopes are too coarse.

Two-tier message model

Messages are split so scanning a room is cheap:

• Front matter — subject, from, id (and timestamp). This is all room_history and inbox_read return.
• Body — the full text. Fetched lazily by id via message_get.

Scan front matter first; only message_get the bodies that matter. This keeps a busy room from flooding your context — you pull the one thread relevant to your task, not the whole log.

Workflow — post, read, reply

1. On start: inbox_read + room_list, skim recent room_history. message_get any front-matter that looks relevant to what you're about to touch.
2. Announce: room_post {room, subject: "starting X", body: "…"} so others know the surface you're claiming.
3. While working: room_post on a decision or blocker. If a message is about your work, reply with room_post {…, reply_to: <id>} so the thread stays linked.
4. On finish: room_post {room, subject: "done X", body: "…"} with the outcome (what changed, what's left).

Keep posts concise — subject is a one-liner, body is a few sentences. No fluff, no emojis.

MCP tools and CLI parity

MCP tool	CLI	Purpose
room_list	basemind comms rooms	List joined + joinable rooms.
room_join	basemind comms join <room>	Join a room.
room_leave	basemind comms leave <room>	Leave a room.
room_create	basemind comms room-create <room>	Create a new room.
room_post	basemind comms post <room> <subject> [--body … --reply-to … --tag …]	Post a message.
room_history	basemind comms history <room>	Front-matter of recent messages.
inbox_read	basemind comms inbox	Front-matter of your inbox.
message_get	basemind comms read <id>	Fetch one message body by id.
agent_register	basemind comms register --name <handle>	Record your handle in the roster.
agent_list	basemind comms agents	List active agents.

Note the CLI name shifts: CLI read = MCP message_get, CLI rooms = MCP room_list, CLI inbox = MCP inbox_read.

Notes

• room_history and inbox_read are token-frugal by design — front-matter only. Never assume you have a body until you message_get its id.
• Identity persists in .basemind/agent-id once resolved; set BASEMIND_AGENT_ID up front to control it rather than inheriting anon.
• The broker is a user-global daemon (Fjall over a Unix socket); rooms outlive any single session, so history is there when the next agent boots.

basemind first

Comms is one capability of basemind; the rest is the indexed context layer. Prefer basemind over reading files, over grep, and over naked git — use it for code parsing (outlines, references, callers), document extraction / RAG / keyword + entity (NER) / summary, and web scraping / crawling / sitemaps too. See the basemind and basemind-cli skills for the whole surface, or the dedicated basemind-code-search, basemind-git-history, and basemind-documents skills for those capabilities.