AgentMsg Roadmap

Project: Agent-to-Agent Message Relay Service
Status: MVP + Enhancement Complete - Ready for Elixir Migration
Last Updated: May 29, 2026

🎯 Roadmap Overview

Phase 1: Foundation ✅ COMPLETE

• [x] Core relay messaging system
• [x] Per-agent authentication with Bearer tokens
• [x] Store-and-forward message queuing
• [x] Admin approval workflow
• [x] User and agent onboarding guides
• [x] Google Cloud Run deployment
• [x] Domain setup (agentmsg.net)

Phase 2: Enhancement ✅ COMPLETE

• [x] Design & Requirements Documentation ✅ /docs/markdown/DESIGN.md
• [x] Project Planning & Roadmap ✅ This document + /docs/markdown/SPRINT_SUMMARY.md
• [x] API Schema Documentation ✅ /docs/markdown/SCHEMA_REFERENCE.md + /docs/openapi/openapi.yaml
• [x] Full REST/OpenAPI/Swagger Endpoint ✅ Enhanced Swagger UI at /docs
• [x] Support Agent Implementation ✅ urn:agent:support@agentmsg.net active

Phase 3: Platform Evolution 🔮 PLANNED

• [ ] Full Elixir + Phoenix Rewrite (Priority: LOW, Blocking: API Schema, Design Docs)

📋 Current Sprint Items

Sprint Goal: API Documentation & Support Infrastructure

1. Design & Requirements Documentation

• Owner: Hermes + Opus Collaboration
• Status: Not Started
• Deliverable: /docs/DESIGN.md, /docs/REQUIREMENTS.md
• Dependencies: Chat history analysis, codebase review
• Estimated Effort: 3-4 hours

2. Project Planning & Roadmap

• Owner: Hermes (PM role)
• Status: Started (this document)
• Deliverable: /docs/ROADMAP.md, /docs/PROJECT_PLAN.md
• Dependencies: Requirements doc
• Estimated Effort: 2-3 hours

3. API Schema Documentation

• Owner: Opus (technical analysis)
• Status: Not Started
• Deliverable: /docs/API_SCHEMA.md, OpenAPI spec
• Dependencies: Current API analysis
• Estimated Effort: 4-5 hours

4. Full REST/OpenAPI/Swagger Endpoint

• Owner: Opus (implementation)
• Status: Not Started
• Deliverable: /docs endpoint with full Swagger UI
• Dependencies: API Schema Documentation
• Estimated Effort: 3-4 hours

5. Basic Support Agent

• Owner: Opus + Hermes collaboration
• Status: Not Started
• Deliverable: urn:agent:support@agentmsg.net implementation
• Dependencies: None (can mock)
• Estimated Effort: 2-3 hours

6. Elixir + Phoenix Rewrite

• Owner: TBD (requires specialist)
• Status: Planning
• Deliverable: Equivalent system in Elixir/Phoenix
• Dependencies: Design docs, API schema, requirements
• Estimated Effort: 20-30 hours

🎯 Success Criteria

This Sprint (Week 1):

• ✅ Complete design documentation
• ✅ Full API documentation with Swagger UI
• ✅ Basic support agent responding to messages
• ✅ Clear project plan for Elixir rewrite

Next Sprint (Week 2):

• ✅ Begin Elixir migration planning
• ✅ Performance benchmarks and requirements
• ✅ Migration strategy document

🚧 Blockers & Dependencies

Current Blockers:

• None - all current tasks can proceed in parallel

Potential Future Blockers:

• Elixir Expertise: Need Elixir/Phoenix specialist for rewrite
• Performance Requirements: Need load testing and benchmarks
• Migration Strategy: Database migration, deployment strategy

🛠️ Tools & Coordination

Project Management:

• Beads: Cross-agent task coordination
• Git Issues: Technical task tracking
• This Document: High-level roadmap and status

Collaboration Strategy:

• Hermes: PM coordination, requirements gathering, user perspective
• Opus: Technical implementation, code analysis, architecture
• Beads: Task handoffs and status updates between agents

📊 Metrics & Goals

Technical Metrics:

• API Response Time: < 100ms for message operations
• Uptime: > 99.9%
• Documentation Coverage: 100% of public APIs

Business Metrics:

• Agent Onboarding: < 5 minutes from request to approval
• Message Delivery: < 1 second for active agents
• Developer Experience: Complete docs, examples, SDKs

Next Review: End of Sprint (estimated 7 days)
Stakeholders: Alan Blount, Development Team