Skip to content

fix/docker telemetry copy#308

Merged
khaliqgant merged 3 commits intomainfrom
fix/docker-telemetry-copy
Jan 26, 2026
Merged

fix/docker telemetry copy#308
khaliqgant merged 3 commits intomainfrom
fix/docker-telemetry-copy

Conversation

@khaliqgant
Copy link
Copy Markdown
Member

@khaliqgant khaliqgant commented Jan 26, 2026

  • fix: correct Claude Code MCP config path
  • feat: add Codex MCP support with TOML config
  • fix: Codex MCP uses project-local config by default
  • docs: add Codex and all supported editors to MCP README
  • fix: MCP install uses absolute paths for nvm users
  • feat: auto-approve agent-relay MCP tools on install
  • fix: set RELAY_SOCKET for project-local MCP installs
  • bring in latest
  • feat: decouple MCP client from dashboard HTTP API
  • fix: MCP client fire-and-forget semantics and protocol alignment
  • fix: preserve MCP config in cloud workspace entrypoint
  • fix: use spawnerName instead of parent in MCP spawn payload
  • fix: resolve race condition in setup agent PTY output and shell escaping
  • feat: add SendEnter mechanism for stuck input recovery
  • fix: MCP protocol alignment and agent name discovery
  • fix: socket auto-reconnect and improved agent name discovery
  • docs: add comprehensive Murmur vs Agent Relay protocol comparison
  • docs: add agent lifecycle and connection management comparison
  • Fix Docker build by copying telemetry workspace

Open with Devin

Agent Relay and others added 3 commits January 26, 2026 02:05
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>
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 e6a88b1 into main Jan 26, 2026
21 checks passed
@khaliqgant khaliqgant deleted the fix/docker-telemetry-copy branch January 26, 2026 05:49
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 potential bugs to report.

View in Devin Review to see 7 additional flags.

Open in Devin Review

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