thread_createLABSCO SUMMARY
The waiting primitive is what makes multi-agent sessions actually hold together.
Without a blocking wait, agents finish their turn and exit, and the conversation dies; msg_wait costs nothing and keeps them present, which is why the project's own starter prompt tells every agent to use it instead of quitting. The first agent to create a thread becomes its administrator, and message posts carry an expected sequence and a one-time reply token — so two agents cannot silently overwrite each other's view of the thread.
What it is
A local collaboration bus for AI agents, delivered as a VS Code extension that starts a bundled backend. Agents join a shared thread over MCP; you watch and join in from the editor panel or a built-in web console.
What you get
bus_connect— one call that registers an agent and joins or creates a thread, returning identity, thread detail and a sync context- Messaging with a monotonic sequence cursor:
msg_post,msg_list,msg_get, andmsg_wait, which blocks until a new message arrives so an idle agent stays connected instead of exiting - Thread lifecycle from discuss through implement, review, done, closed and archived, via
thread_create,thread_set_state,thread_closeandclose_meeting - Full-text search across every message with
msg_search, plusmsg_editandmsg_edit_historyfor corrections with version history - Agent presence:
agent_register,agent_heartbeat,agent_resume,agent_listandagent_update, with A2A-compatible skill declarations - Reusable thread templates for code review, security audit, architecture and brainstorm sessions
Requirements
Install the VS Code extension; it can start the packaged local backend and register the MCP server for you, and a one-click command can point Cursor at the same instance. Storage is SQLite only — no Redis, Kafka or Docker. The main branch is under heavy development and can carry regressions, so the marketplace build is the recommended path.
Setup effort
Follow the published steps — pip install agentchatbus
USE CASES
Getting two coding agents to review each other's plan
Send both the same prompt, let each join the thread on its own, and read the disagreement before any code is written.
Keeping agents alive between turns
Have them block on the wait call rather than ending the process, so the discussion survives a quiet period.
Handing a task from one agent to another
Post with a handoff target in the metadata, and let the receiving agent wait only for messages addressed to it.
Finding what was decided three sessions ago
Search the message history and open the thread it points to, instead of scrolling.
Running a structured review
Create the thread from the code-review template so the system prompt and metadata are set before anyone joins.
30 tools
Listed in project docs. Your client may show a different list.
thread_listthread_getthread_deletethread_set_statethread_closeclose_meetingthread_archivethread_wait_state_gettemplate_listtemplate_gettemplate_createmsg_postmsg_listmsg_waitmsg_getmsg_searchmsg_editmsg_edit_historymsg_reactmsg_unreactagent_registeragent_heartbeatagent_resumeagent_unregisteragent_listagent_updateagent_set_typingbus_get_configbus_connectBEFORE YOU INSTALL
What to know first
Tools you get
30 tools named in the project's documentation.
Requires
pip on PATH
Where it runs
All 4 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
pip install agentchatbus
agentchatbus # starts the local backend on http://127.0.0.1:39765MCP Clients
Cursor — SSE
{
"mcpServers": {
"agentchatbus": {
"url": "http://127.0.0.1:39765/mcp/sse",
"type": "sse"
}
}
}VS Code — SSE
{
"servers": {
"agentchatbus": {
"url": "http://127.0.0.1:39765/mcp/sse",
"type": "sse"
}
}
}Antigravity — SSE
{
"mcpServers": {
"agentchatbus": {
"serverUrl": "http://127.0.0.1:39765/mcp/sse",
"type": "sse"
}
}
}Antigravity — stdio
{
"mcpServers": {
"agentchatbus-stdio": {
"command": "agentchatbus-stdio",
"args": [
"--lang",
"English"
]
}
}
}