Release Notes: v0.3.0¶

Release Date: 2026-03-16

Overview¶

AgentComms v0.3.0 introduces multi-agent support, enabling AI agents to discover and communicate with each other. This release also adds unified JSON configuration, inbound message tools, and a comprehensive documentation site.

Highlights¶

Multi-Agent Communication: Agents can discover each other and send messages for task delegation and coordination
Unified JSON Configuration: Single config.json file replaces split env vars + YAML configuration
Inbound Message Polling: MCP tools for agents to check for human messages during long tasks
MkDocs Documentation Site: Comprehensive documentation at plexusone.github.io/agentcomms

New Features¶

Multi-Agent Tools¶

Tool	Description
`list_agents`	Discover available agents and their status (online/offline)
`send_agent_message`	Send message to another agent for coordination

Agent-to-agent messages arrive with source prefix:

[from: frontend] Can you help me with the API implementation?

Inbound Message Tools¶

Tool	Description
`check_messages`	Poll for human messages sent via Discord/Telegram
`get_agent_events`	Get all events (messages, interrupts) with pagination
`daemon_status`	Check if the daemon is running

Unified JSON Configuration¶

# Generate configuration file
agentcomms config init

# Validate configuration
agentcomms config validate

Configuration supports environment variable substitution:

{
  "version": "1",
  "agents": [{"id": "claude", "type": "tmux", "tmux_session": "dev"}],
  "chat": {
    "discord": {"token": "${DISCORD_TOKEN}"}
  }
}

Daemon Infrastructure¶

The daemon provides Human → Agent communication:

Actor-style Router: Per-agent goroutines for isolated event processing
Event Store: SQLite database via Ent ORM
tmux Adapter: Send messages to agents running in tmux panes
Chat Transport: Receive messages from Discord, Telegram, WhatsApp

CLI Commands¶

agentcomms daemon          # Run inbound daemon
agentcomms status          # Check daemon status
agentcomms agents          # List registered agents
agentcomms send <id> "msg" # Send message to agent
agentcomms interrupt <id>  # Send Ctrl-C to agent
agentcomms events <id>     # View agent events
agentcomms reply <ch> "msg"# Reply to chat channel
agentcomms channels        # List channel mappings
agentcomms config init     # Generate config file
agentcomms config validate # Validate config

Architecture Changes¶

Agent Status Tracking¶

Agents now have tracked status:

online: Registered with router and processing events
offline: Not currently active

Status updates automatically on register/unregister.

Event Schema¶

Events now include source_agent_id to distinguish:

Human → Agent messages (source_agent_id = "")
Agent → Agent messages (source_agent_id = sending agent)

IPC Protocol¶

New agent_message method for cross-agent routing:

{
  "method": "agent_message",
  "params": {
    "from_agent_id": "frontend",
    "to_agent_id": "backend",
    "message": "Can you help with the API?"
  }
}

Documentation¶

Dependencies¶

Package	Version	Change
entgo.io/ent	v0.14.5	Database ORM
modernc.org/sqlite	v1.46.1	Pure Go SQLite
modelcontextprotocol/go-sdk	v1.4.1	MCP protocol
assistantkit	v0.12.0	Plugin configuration
tablewriter	v0.0.5	Pinned for ent compatibility

Full Changelog¶

See CHANGELOG.md for the complete list of changes.