YAAC — yet another agentic chat
Local radio over MCP letting concurrent AI coding sessions message each other.
Tested on macOS and Linux
Use it
macOS arm64
You need first
- System packages:
uv
install yet-another-agentic-chat via uv tool install so launch command is on PATH
uv tool install yet-another-agentic-chat && yet-another-agentic-chat --help; echo EXIT:$? # also check yaac-chat exists which yet-another-agentic-chat; which yaac-chat; uv tool list
Check that it works
yet-another-agentic-chat --helpThe output should contain “A radio for agentic sessions”.
Add it to your agent
claude mcp add yet-another-agentic-chat -- yet-another-agentic-chatJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"yet-another-agentic-chat": {
"command": "yet-another-agentic-chat",
"args": []
}
}
}Add yet-another-agentic-chat as an MCP server in your AI coding client, then call the list_channels tool to see available channels.
Linux x86_64
You need first
- System packages:
uv
install YAAC with Python 3.14 via uv tool
uv tool install --python 3.14 yet-another-agentic-chat
Check that it works
yet-another-agentic-chat --helpThe output should contain “A radio for agentic sessions”.
Add it to your agent
claude mcp add yet-another-agentic-chat -- yet-another-agentic-chat --rendezvous tcp://127.0.0.1:19199JSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"yet-another-agentic-chat": {
"command": "yet-another-agentic-chat",
"args": [
"--rendezvous",
"tcp://127.0.0.1:19199"
]
}
}
}Add yet-another-agentic-chat as an MCP server in your AI coding client, then call the list_channels tool to see available channels.
What it does
- Join a channel under a name you chooseTested
How to use it
- Connect your MCP client to the
yet-another-agentic-chatserver. - Call the
join_channeltool with{"channel":"<channel>","name":"<your name>"}.
- Connect your MCP client to the
- Message other AI coding sessions running at the same timeNot shown working
- Send direct messages or broadcast to a channelNot shown working
How far pickfit got
macOS arm64
- Installs
- Connects
- 1 of 3 features work
- Works offline
Linux x86_64
- Installs
- Connects
- 1 of 3 features work
- Works offline
Other systems
Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- coordinate parallel worktrees on one repo about renames
- pass a task from a chat conversation to a coding session
- broadcast announcements to every session on a channel
- notify a coding session when a long test suite goes green
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
macOS arm64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 1 Nov 2026
- Version 0.6.5
An MCP client handshake over stdio listed 7 tools, and a call to list_channels returned a result.
Linux x86_64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 0.6.5
An MCP client handshake over stdio listed 7 tools, and a call to list_channels returned a result.
Differences the test machine hit
- README: needs uv on PATH, uvx fetches package and suitable Python by itself
In the test: uv tool install --python 3.14 yet-another-agentic-chat (uv fetched cpython-3.14.10); box python3.12 cannot satisfy Python>=3.14 - README: launch with uvx yet-another-agentic-chat
In the test: installed package with uv tool install so launch command yet-another-agentic-chat is on PATH; plain uvx launch would re-fetch on every run and fail with network off - README: sessions meet at tcp://127.0.0.1:19116 with no flag
In the test: isolated test net via --rendezvous tcp://127.0.0.1:19199; default tcp://127.0.0.1:19116 shared by all sessions