agmsg

Stop copy-pasting between your AI coding agents

Open Source

Developer Tools

Artificial Intelligence

GitHub

Visit WebsiteSee on Product HuntTwitter ⧉Github ⧉

forgive my dumb ass for asking this. still an AI noob. for any conversation that happens in claude for instance (not code related), will this help it migrate to say antigravity?

the sqlite-as-message-bus choice is the part i like — no daemon is the right call. the thing i'd worry about with multiple claude code instances in one room is two of them grabbing the same task before either writes back. how do you handle the claim/lock step?

I'm also thinking about how to pit several neural networks against each other to create the best results only for the topic of YouTube videos.

The "sitting between two systems being their courier" framing is painfully accurate - I do this every day with Claude + a browser-driving agent. Shared SQLite over MCP is the right primitive: zero dependency hell, persistent across sessions, and you can grep history later. Following.

The copy-paste shuffle between Cursor, Claude Code and the rest is a real daily tax, so a shared message bus between agents is a smart framing. Does it preserve context and diffs on handoff, or mainly the prompt text?

The persistent room is the part I'd actually use day to day, the 'agents talking' framing kind of undersells it! Does agmsg arbitrate turns at all (a lock, a token) or is sqlite just guaranteeing nobody drops a message and ordering stays the agents' problem?

been playing the copy-paste courier between claude code and codex for months - feels embarrassing in hindsight. the sqlite approach is just right, no extra process to manage and the whole thread is right there to inspect. curious how turn-taking holds up with 3+ agents but the 2-agent case is exactly what i need

Treating agent-to-agent communication as a first-class primitive rather than bolting it on with shared clipboard or file hacks is genuinely clever. We've run into real pain keeping context synchronized across parallel agent tasks, where state drift creates subtle bugs. How do you handle concurrent write conflicts when two agents message the same SQLite channel simultaneously?

The agent-to-agent message routing is the right abstraction. Instead of shared memory you're treating agents as async message consumers. We've hit context fragmentation when chaining Claude with specialized tools and the copy-paste tax compounds fast. How does agmsg handle partial context handoffs when one agent's output exceeds another's context window limit?

the part that jumps out isn't the agents talking to each other — it's that the room is persistent. it's one sqlite file you can open with sqlite3 and read the whole thread, start to finish. running claude code in a plan → implement → review loop, what always bit me was context dying with each subagent, so i'd hand-roll a state file to carry decisions across passes. a room that outlives the session is exactly that, minus the bookkeeping.

The human courier btw two AIs line made me laugh because that's basically what I've been doing lately. How well does this hold up when more than two agents are involved?

For me the copy-paste isn't even the worst part... it's that the second agent loses the why and confidently rewrites stuff the first one got right. Non-technical builder bouncing between Claude Code and Cursor daily. Does agmsg carry intent across the handoff, or just the code and context?

This is exactly the kind of weird but practical tool that makes sense once you use multiple coding agents. Copying output from Claude Code into Codex and back again gets old fast. A simple SQLite-based “room” for agents to talk to each other feels much cleaner than turning the human into the message bus.