How jake-edwards-ei/agentchattr works
agentchattr is a local multi-agent chat server: people and agents share persistent channels, and @mentions wake terminal agents so they can read context and respond. The core loop runs from browser or MCP message entry through routing, wrapper dispatch, and agent replies; the loop guard limits agent-to-agent hops. Jobs, roles/rules, schedules, archives, and structured multi-agent sessions extend that collaboration workflow. The README documents these capabilities, but sampled source does not establish every subsystem’s internal wiring, so those links are shown conservatively.
Main entry points: app.py Web Server · wrapper.py Agent Wrappers · mcp_bridge.py MCP Tools · session_engine.py Session Engine
Components 22
Chat Interaction
- Chat UI
static/chat.js - Channels UI
static/channels.js - Web Server
app.py - Sessions UI
static/sessions.js
Agent Coordination
- Mention Router
router.py - Agent Registry
registry.py - Agent Wrappers
wrapper.py - MCP Tools
mcp_bridge.py - MCP Proxy
mcp_proxy.py
Work Management
- Jobs
jobs.py - Schedules
schedules.py - Rules
rules.py - Chat Archive
archive.py - Summaries
summaries.py - Session Engine
session_engine.py
Persistence
- Chat Store
store.py - Session Store
session_store.py - Session Templates
session_templates - Configuration
config_loader.py
Other components
- Human
- Coding Agents
- Agent Terminals
Connections 28
- Human → Chat UI: sends messages
- Chat UI → Web Server: WebSocket events
- Channels UI → Web Server: channel commands
- Web Server → Chat Store: stores messages
- Web Server → Mention Router: routes mentions
- Web Server → Agent Registry: checks agents
- Web Server → Agent Wrappers: triggers agents
- Agent Wrappers → Agent Terminals: injects prompts
- Agent Terminals → Coding Agents: runs CLI
- Coding Agents → MCP Tools: calls tools
- MCP Tools → Chat Store: reads and writes
- MCP Tools → Jobs: updates jobs
- MCP Proxy → MCP Tools: proxies MCP
- Web Server → Jobs: handles job requests
- Web Server → Schedules: handles schedule requests
- Web Server → Rules: handles rule requests
- Web Server → Chat Archive: handles archive requests
- Web Server → Summaries: creates summaries
- Sessions UI → Web Server: session requests
- Web Server → Session Engine: coordinates sessions
- Session Engine → Session Store: updates runs
- Session Engine → Chat Store: observes messages
- Session Store → Session Templates: loads templates
- Web Server → Configuration: loads settings
- Web Server → Chat UI: WebSocket updates
- Web Server → Agent Wrappers: routes selected agents
- Agent Wrappers → Web Server: agent replies
- Mention Router → Agent Wrappers: selects targets