Coordinate peer CLI agents with agmsg
Let Claude Code, Codex, Gemini CLI, Copilot CLI, and other terminal agents exchange messages through a shared local SQLite channel.
npx skills add agentskillexchange/skills --skill coordinate-peer-cli-agents-with-agmsg
npx agmsg or npm i -g agmsg && agmsg install, then restart the target CLI agents. Claude Code users can also add the plugin marketplace with /plugin marketplace add fujibee/agmsg and install agmsg@fujibee-agmsg before invoking /agmsg.Use agmsg when an operator needs several CLI agents to coordinate as peers without copy-pasting updates between tools. The workflow is: install agmsg, join or create a team, give each agent a stable identity, check inboxes, send messages, replay history, and optionally spawn or despawn peer sessions for review or implementation work. Invoke this instead of using each product normally when the job depends on handoff between independent agent sessions such as Claude Code asking Codex for review, Gemini sending research notes, or a lead agent delegating work to a separate terminal. The scope boundary is local peer-agent messaging and session coordination via agmsg’s scripts and skill files. It is not an MCP server, hosted collaboration product, generic message broker, or broad multi-agent framework listing.
What this skill actually does
Inputs and prerequisites: bash, sqlite3, agmsg scripts, Claude Code/Codex/Gemini CLI/Copilot CLI/Antigravity/OpenCode as applicable.
Setup notes: Run npx agmsg or npm i -g agmsg && agmsg install , then restart the target CLI agents. Claude Code users can also add the plugin marketplace with /plugin marketplace add fujibee/agmsg and install agmsg@fujibee-agmsg before invoking /agmsg .
Source and verification boundary: use https://github.com/fujibee/agmsg as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.