fujibee/agmsg: README-based editorial guide

fujibee/agmsg describes itself in the README as "Cross-vendor messaging for CLI AI coding agents , let Claude Code, Codex, Gemini & Copilot talk to each other in one team. Bash + SQLite, no daemon, no framework.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "agmsg", the README says: Cross-agent messaging for CLI AI agents. No daemon, no network, no complexity.. That establishes the project's stated boundary, not a production test.

The README's "agmsg" section gives a useful starting point for deciding whether the project fits: Not subagents. agmsg connects peer sessions across different tools. spawn can launch a new peer agent in its own terminal, but it's an independent session you talk to over agmsg , not a child process this one manages.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Not MCP. No MCP server, no extra runtime , just bash + sqlite3.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "agmsg". The source evidence includes: You stop being the copy-paste courier between your agents. Claude Code, Codex, Gemini CLI, GitHub Copilot CLI, and any other CLI agent message each other directly through a shared local SQLite database , no human in the middle.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: npx agmsg # one-shot, no global install # or npm i -g agmsg && agmsg install When the README contains no runnable command, this article does not invent one. Open its "Quick Start" section and confirm system dependencies, default ports, and first-run initialization before using a public server.