Skip to content

docs: add comprehensive Murmur vs Agent Relay protocol comparison#307

Merged
khaliqgant merged 2 commits intomainfrom
feature/murmur-comparison
Jan 26, 2026
Merged

docs: add comprehensive Murmur vs Agent Relay protocol comparison#307
khaliqgant merged 2 commits intomainfrom
feature/murmur-comparison

Conversation

@khaliqgant
Copy link
Copy Markdown
Member

@khaliqgant khaliqgant commented Jan 26, 2026

Summary

Adds detailed competitive analysis comparing Murmur's end-to-end encrypted cross-network messaging with Agent Relay's low-latency local IPC.

Key Findings

Complementary Systems:

  • Murmur: 100-500ms latency, E2E encrypted (Signal Protocol), offline-first, cross-network
  • Agent Relay: <5ms latency, local IPC, real-time coordination, synchronous messaging

Improvement Opportunities for Agent Relay

High Priority

  1. Message persistence - Optional SQLite storage for critical messages
  2. Backpressure implementation - Bounded queues, BUSY responses
  3. Session token security - Expiration, rotation, replay protection

Medium Priority

  1. Error code taxonomy - Complete enumeration beyond just "STALE"
  2. Attachment support - Reference-based with chunked upload
  3. TTL + auto-cleanup - Prevent unbounded memory growth

Content

The comparison document covers:

  • Transport layer differences (HTTPS+SSE vs Unix Domain Sockets)
  • Message format and structure (3-layer encryption vs single envelope)
  • Security models (cryptographic vs trust-based)
  • Delivery guarantees (store-and-forward vs online-only)
  • Session management (stateless vs stateful)
  • Cryptography deep dive (X3DH, Double Ratchet, etc.)
  • Synchronous messaging (Agent Relay's unique feature)
  • Integration scenarios (hybrid architecture, gateway pattern)

Test Plan

Documentation change only - no code changes.

🤖 Generated with Claude Code


Open with Devin

Add detailed competitive analysis comparing Murmur's E2E encrypted
cross-network messaging with Agent Relay's low-latency local IPC.

Key findings:
- Complementary systems for different use cases
- Murmur: 100-500ms latency, E2E encrypted, offline-first
- Agent Relay: <5ms latency, local IPC, real-time coordination
- Identified improvement opportunities for Agent Relay:
  * Message persistence (HIGH)
  * Backpressure implementation (HIGH)
  * Error code taxonomy (MEDIUM)
  * Session token security (MEDIUM)
  * Attachment support (MEDIUM)

Research includes detailed protocol analysis, security model comparison,
and hybrid integration patterns.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Adds detailed section explaining how Murmur and Agent Relay handle
agent lifecycle, connection management, and message flow.

Key findings:
- Murmur: Agent-managed lifecycle (explicit control)
  * CLI approach: Manual background process with webhooks
  * MCP approach: Pull-based polling via MCP tools
  * Developer manages SSE connection and message fetching

- Agent Relay: Wrapper-managed lifecycle (automatic)
  * relay-pty maintains UDS connection automatically
  * Push-based message injection into agent PTY
  * No background process management needed

Includes code examples from both projects showing:
- SSE connection management with auto-reconnect
- Exponential backoff retry logic
- MCP server tool implementation
- relay-pty wrapper automatic injection

Developer experience comparison shows Agent Relay's simplicity
(just use output patterns) vs Murmur's explicit control model.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@khaliqgant khaliqgant merged commit f6ce50f into main Jan 26, 2026
21 of 22 checks passed
@khaliqgant khaliqgant deleted the feature/murmur-comparison branch January 26, 2026 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant