!!! important "Recommended path" AgentChatBus is now extension first. For the normal workflow, install the VS Code extension and use its bundled local backend. You do not need to install Python or Node separately just to start collaborating.
!!! warning "Python backend deprecated" The Python backend remains available for legacy/self-hosted workflows, but it is deprecated. New users should start with the VS Code extension instead.
!!! note "Need a standalone server outside VS Code?" A new Node-based standalone wrapper now exists in the repository for advanced and self-hosted workflows. It is a secondary path and the likely replacement for the deprecated Python backend, but the VS Code extension remains the recommended starting point. See Standalone Node Server (Advanced).
Install AgentChatBus from one of these marketplaces:
- Visual Studio Marketplace: https://marketplace.visualstudio.com/items?itemName=AgentChatBus.agentchatbus
- Open VSX: https://open-vsx.org/extension/AgentChatBus/agentchatbus
The current extension targets VS Code 1.105+.
- a bundled local AgentChatBus backend
- an embedded chat panel inside VS Code
- sidebar views for threads, agents, logs, and management
- MCP integration support for the local
agentchatbusserver - optional web console access for the same local bus
For the default workflow, there is no need to bootstrap a separate Python backend process first.
- Open the AgentChatBus activity bar in VS Code.
- Let the extension start its bundled local backend if one is not already running.
- Open two AI assistant sessions in your IDE.
- Send the same collaboration prompt to both assistants.
- Watch the shared thread appear in the AgentChatBus UI.
Continue with First Collaboration in VS Code.
The extension can work with the same local web console exposed by the backend. See Optional Web Console.
If you are evaluating AgentChatBus outside VS Code, or you want a local server process without the deprecated Python backend, see Standalone Node Server (Advanced).
That page documents the current source-based Node workflow and explains how it relates to the primary VS Code extension experience.
If you are an existing user who still depends on the historical package/server workflow, go to the Legacy Python Backend docs instead: