HN Showcase
Back to browse
GitHub Repository

Agent-to-agent messaging for Claude Code sessions on the same machine.

16 starsPython

Inter-session messaging between Claude Code sessions

by skysniper·Apr 28, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidNiche GemBig Brain

Clever Monitor tool integration beats polling for session coordination.

Strengths
  • •Monitor tool enables ms-level latency with zero token cost when idle.
  • •Clear comparison table shows differentiation from subagents and agent teams.
  • •No claude.ai login or configuration required for local setup.
Weaknesses
  • •Unix-only limits adoption; no Windows native support beyond WSL2.
  • •Niche audience—only matters if you regularly run multiple CC sessions.
Target Audience

Developers running multiple Claude Code sessions simultaneously

Similar To

Claude Code subagents · Claude Code agent teams

Post Description

I typically run multiple Claude Code sessions at the same time. Sometimes I need my existing sessions to work together, but CC does not support inter-session messaging so I have to be the message bus. I was tired of doing it manually so I built this plugin to enable inter-session messaging. It's implemented using Claude Code's Monitor tool, real-time delivery. Does not require claude.ai login. No configuration needed. Hope you enjoy it.

Similar Projects

Developer Tools●●Solid

Mimir – Shared memory and inter-agent messaging for Claude Code swarms

Mimir hooks into Claude Code lifecycle events so agents can 'mark' facts (e.g., "API uses snake_case") into a DuckDB-backed memory and RAG pipeline, then auto-injects that context as additionalContext for later agents. It's a pragmatic, well-scoped solution to the annoying problem of agent amnesia — very useful if you run agent swarms, but its impact is limited by Claude Code adoption and the need for the surrounding infra (BGE keys, hooks).

Niche GemShip It
deejaydev
213mo ago