--- name: Agent Messaging slug: agent-messaging-2 category: AI Engineering description: Agent Messaging lets CLI AI agents like Claude Code, Codex, Gemini CLI, and GitHub Copilot send messages to each other through a shared local SQLite database with no daemon or network. Use it to coordinate multi-agent workflows, pass code reviews, or share context between peer sessions. github: "https://github.com/fujibee/agmsg" language: Shell stars: 1452 forks: 139 install: "npx degit https://github.com/fujibee/agmsg ~/.claude/skills/agmsg" installs_to: ~/.claude/skills/agmsg source_path: SKILL.md collection_size: 1 category_size: 2451 added: 2026-08-19T07:27:19.202Z last_synced: 2026-08-19T07:27:19.202Z canonical_url: "https://dirskills.com/skills/agent-messaging-2" --- # Agent Messaging Agent Messaging lets CLI AI agents like Claude Code, Codex, Gemini CLI, and GitHub Copilot send messages to each other through a shared local SQLite database with no daemon or network. Use it to coordinate multi-agent workflows, pass code reviews, or share context between peer sessions. **Install:** ```bash npx degit https://github.com/fujibee/agmsg ~/.claude/skills/agmsg ``` ## README # Agent Messaging **IMPORTANT: Always use the provided scripts. NEVER directly read or edit config files, DB, or team data. There is NO register.sh — use join.sh to join a team.** **Shell requirement:** All agmsg scripts are Bash scripts. Always execute them via `bash`, never via PowerShell or cmd directly. If your default shell is not Bash (e.g. PowerShell on Windows), wrap every command with `bash -lc '...'`. Example: `bash -lc '~/.agents/skills/agmsg/scripts/send.sh myteam alice bob "hello"'`. Do NOT construct DB paths manually — the scripts handle path resolution internally. If you need to redirect storage, use `AGMSG_STORAGE_PATH` (the supported override). ## How to use ### Step 0: First-run bootstrap agmsg keeps its SQLite database, team registry, and runtime state under `~/.agents/skills/agmsg/`. The `./install.sh` install path creates that tree; the Claude Code plugin install path does not (the plugin marketplace flow only drops the skill content into `~/.claude/plugins/cache/`). Before any other command, bootstrap if needed: ```bash if [ ! -d ~/.agents/skills/agmsg ]; then # Locate the plugin install script (any version), run it once. installer=$(ls ~/.claude/plugins/cache/fujibee-agmsg/agmsg/*/install.sh 2>/dev/null | head -1) if [ -n "$installer" ]; then bash "$installer" --cmd agmsg else echo "agmsg not installed. Either:" >&2 echo " - run ./install.sh in the agmsg repo, or" >&2 echo " - install via /plugin marketplace add fujibee/agmsg && /plugin install agmsg@fujibee-agmsg" >&2 exit 1 fi fi ``` After this runs once, `~/.agents/skills/agmsg/` is populated and you can skip Step 0 on future invocations. ### Step 1: Check identity ```bash ~/.agents/skills/agmsg/scripts/whoami.sh "$(pwd)" # type: claude-code, codex, gemini, antigravity, copilot # Returns: agent=... / multiple=true ... / suggest=true ... / not_joined=true ... ``` ### Step 2a: If not in a team — join one Before first-time setup, inspect the user's request. If they ask to join, import, or bring in a team that already exists on a server, do not run `join.sh`. Go directly to the `remote pull` command under Step 2b. Before pulling, run `team-list.sh --json --scope all`; if a same-named local team has `binding_state` `none` or `disconnected`, stop and ask the user how to proceed. After pull succeeds, return here so the user can register a new local agent in the team that pull just created. Ask the user for a team name. If it's an existing team, run `team.sh ` first to see the current roster and note the names already in use. Look for a naming convention already in play (e.g. a shared base name with role and number suffixes (`-`), or names derived from the team name) and, when one exists, propose 2-3 unused names that extend it; otherwise propose 2-3 short, distinctive identity names (not a bare tool-type label like `codex`/`cc`). Either way, names must not collide with the roster. For a brand-new team, skip the roster check and just ask. Then run: ```bash ~/.agents/skills/agmsg/scripts/join.sh "$(pwd)" [--force] ``` Do NOT manually edit config files. Always use join.sh. If the name was recently renamed away with `rename.sh`, join.sh refuses to revive it (printing the new name it maps to) instead of silently re-registering it — this guards against a CLI slash-command history resubmitting `actas ` after a rename. Pass `--force` only for a deliberate, unrelated reuse of that exact name. ### Step 2b: If already in a team — execute command **Default (no arguments): IMMEDIATELY check inbox. Do NOT ask what to do.** ```bash # Check inbox (marks messages as read) — DEFAULT action ~/.agents/skills/agmsg/scripts/inbox.sh # Send a message (from/to must already be registered in ; add --force to bypass) ~/.agents/skills/agmsg/scripts/send.sh "" [--force] # Message history ~/.agents/skills/agmsg/scripts/history.sh [agent_id] [limit] # Export a team's message history as JSONL — one message_sent record per line, # chronological. Default to stdout (pipeable); --out writes a file. # --agent limits to one agent; --limit keeps the most recent N (omit = all # currently retained). Output is plaintext (the local store is plaintext). ~/.agents/skills/agmsg/scripts/export.sh --team [--agent ] [--limit N] [--out ] # List team members ~/.agents/skills/agmsg/scripts/team.sh # List every locally known team (read-only, secret-free — "agmsg team list"). # Distinct from `team.sh ` above: check for "team list" FIRST so # "list" is never mistaken for a team name. --json emits a strict, # versioned object ({schema_version, teams: [{name, remote_team_id, scope, # binding_state}]}) and exits non-zero with NO payload if any team was # unreadable or the count was truncated — never a partial list dressed up # as complete. See scripts/team-list.sh's own header comment for the exact # enums and why onboarding_state/promote_eligible/blocked_reason are # deliberately NOT in this schema yet (their meaning depends on ADR 0010, # which hasn't landed). ~/.agents/skills/agmsg/scripts/team-list.sh [--json] [--scope all|project] [] # Leave a team ~/.agents/skills/agmsg/scripts/leave.sh # Rename a team (moves dir, updates config + messages). # After renaming, each existing member should re-run whoami.sh to refresh # their cached team name in any running session. ~/.agents/skills/agmsg/scripts/rename-team.sh # Show the installed version — the git-describe provenance string recorded at # install time (tag + commits-since + abbreviated commit, plus -dirty when # installed from a tree with uncommitted changes). See #117. ~/.agents/skills/agmsg/scripts/version.sh # Clear registrations for the current project/type. # A trailing additionally releases any actas exclusivity locks # this session held on so peers can pick them up immediately. ~/.agents/skills/agmsg/scripts/reset.sh "$(pwd)" [agent_id] [session_id] # Set delivery mode for this project. # monitor — real-time push via SessionStart + Monitor tool (claude-code only) # turn — Stop-hook pulls at the end of each assistant turn # both — monitor primary, turn as fallback # off — no automatic delivery ~/.agents/skills/agmsg/scripts/delivery.sh set "$(pwd)" ~/.agents/skills/agmsg/scripts/delivery.sh status "$(pwd)" # Multiple roles per project (one CC = one active role). # Claude Code: `actas` claims an exclusivity lock for across sessions # and restarts the Monitor filtered to only; peer watchers stop # subscribing to while this session holds the lock. `drop` releases. # Codex: actas is send-side only (no stable session_id during slash commands # → no peer-visible lock). See README "Codex caveat" for details. # If is new and none was given upfront (bare `actas`, or the user asks # for a suggestion), check the target team's roster first (team.sh ). # Look for a naming convention already in play (e.g. a shared base name with # role and number suffixes (-), or names derived from the # team name) and, when one exists, propose 2-3 unused names that extend it; # otherwise propose 2-3 short, distinctive names. Either way, names must not # collide with the roster. Ask the user to pick before continuing. ~/.agents/skills/agmsg/scripts/actas-claim.sh "$(pwd)" "$session_id" ~/.agents/skills/agmsg/scripts/reset.sh "$(pwd)" "$session_id" # (Both of the above are normally driven by `/agmsg actas ` and # `/agmsg drop ` slash commands, which also handle the Monitor # TaskStop + relaunch dance described in the cmd template.) # Spawn a NEW agent process that takes an actas identity on boot. # Pre-joins to a team, then launches the agent CLI in a tmux pane/window # (when run inside tmux) or a new OS terminal, with `/agmsg actas ` as the # initial prompt. By default it BLOCKS until the new agent's watcher attaches # (prints `status=ready`), so a leader can send work right after spawn returns # without losing it to the agent's cold start. claude-code/codex only; macOS # primary, Linux/Windows best-effort. Non-tmux + no usable terminal (headless) # errors out. # --project project to launch in (default: $PWD) # --team team to join into (default: auto-resolved from project) # --window new tmux window instead of splitting the current one # --split h|v tmux split direction (default h) # --terminal terminal command template ({cmd} = path to the boot # script) for the non-tmux path; overrides $AGMSG_TERMINAL # / config spawn.terminal. macOS default uses `open -a` # (no Automation/TCC permission prompt). # --no-wait don't block on readiness (fire-and-forget) # --ready-timeout N seconds to wait for readiness (default 90; on timeout # prints status=timeout and exits 3). Codex skips the # wait (it has no Monitor). # --boot-prompt hand the new agent an initial task: the boot prompt # becomes the actas command followed (newline-separated) # by , so it claims its identity AND starts the task # in its first turn. The only way to give a one-shot goal # to a codex peer (no Monitor → a post-spawn send to its # idle session is never noticed). ~/.agents/skills/agmsg/scripts/spawn.sh [options] # Tear down a spawned member — the inverse of spawn. # Default (graceful): sends a `ctrl:despawn` control message to ; the # member's watcher drops its own role (releasing the actas lock + registration) # and closes its own tmux pane, ending the agent. Blocks until the lock releases # (--timeout, default 30s) then prints `status=ok`; on timeout prints # status=timeout and exits 3 (retry with --force). Only an exclusive watcher # dedicated to acts on it — the despawning session is never torn down. # --force: skip the message and tear the member down from the placement recorded # at spawn time (kill its tmux pane/window, drop its registration) — for a dead # watcher or a codex member (no Monitor). A hand-started member with no placement # record can't be --forced. # --force tear down from the recorded placement, no message # --timeout N seconds to wait for graceful teardown (default 30) ~/.agents/skills/agmsg/scripts/despawn.sh [--force] [--timeout N] ``` ### Rename If argument starts with "rename" but not "rename-team": 1. Accept only an explicit user request. Parse either ` `, or ` ` only when this agent belongs to exactly one team. 2. Never invent either name. Before execution, repeat the resolved team, old name, and new name and ask the user to confirm. Wait for confirmation. 3. Run: `bash ~/.agents/skills/agmsg/scripts/rename.sh ` 4. Show the result. For a connected team, the `member_renamed` journal event propagates the rename to other machines. If argument starts with "rename-team": 1. Accept only an explicit user request. Parse ` `. 2. Never invent either team name. Before execution, repeat the old and new team names and ask the user to confirm. Wait for confirmation. 3. Run: `bash ~/.agents/skills/agmsg/scripts/rename-team.sh ` 4. Show the result. ### Remote sync Remote setup is no-auth. Do not ask for a token or create one. If argument starts with "remote connect": 1. Parse the required `--endpoint ` and ``, plus optional `--e2ee`. 2. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh connect --endpoint [--e2ee] ` 3. Show the output to the user. Plain sync is the default; pass `--e2ee` only when the user explicitly requests end-to-end encryption. The choice is fixed by the first connect. 4. End by showing this copy-paste command for the other machine, with the actual endpoint and team substituted: `bash ~/.agents/skills/agmsg/scripts/remote.sh pull --endpoint ` If argument starts with "remote pull": 1. When the user asks to join or bring in a team that already exists on a server, NEVER use `join.sh`, create a team, or create a same-named local team. Always use remote pull. 2. Before pulling, check for a same-named local team. If one already exists without an active remote connection, stop and ask the user how to proceed; do not overwrite, merge, connect, or rename it on your own. 3. Parse the required `--endpoint ` and ``, plus optional `--team-id `. 4. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh pull --endpoint [--team-id ] ` 5. Show the output to the user. Machine B needs its own install, not just its own environment variables. Only `remote.sh`, `remote-sync.sh`, `key.sh` and the two internal helpers read `AGMSG_SYNC_CONNECTION_DIR`; `send.sh`, `history.sh`, `team.sh` and `inbox.sh` resolve the team config from the install directory. So a pull driven by environment variables alone succeeds, and the send that is supposed to confirm it then reports the team as missing — the failure lands one step after the cause. See "Use a separate install for testing" in `docs/remote-setup.md`. If argument starts with "remote unlock": 1. Parse ``, `--bundle `, and `--confirm-digest `. 2. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh unlock --bundle --confirm-digest ` 3. The snapshot digest must be compared over a separate live channel. Never infer or auto-confirm it. The bundle is permanent secret key material; tell the user to transfer and handle it only through their own trusted channel, never by pasting it into agent chat. 4. Show the complete result, including the imported-envelope count and engine PID. 5. The advanced form with repeatable `--snapshot` plus `--identity` or `--identity-stdin` remains available when explicitly requested. If argument starts with "remote status": 1. Parse an optional `` and `--json`. 2. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh status [] [--json]` 3. Show the output to the user. If argument starts with "remote sync start": 1. Parse the required ``. 2. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh sync start ` 3. Show the output to the user. If argument starts with "remote disconnect": 1. Parse the required ``. 2. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh disconnect ` 3. Show the output to the user. If argument starts with "remote forget": 1. Parse the required ``. This permanently deletes that team's local roster, history, keys, trust, and sync state, but never changes the server. 2. Do not add `--yes` yourself. Run: `bash ~/.agents/skills/agmsg/scripts/remote.sh forget ` 3. The command requires the user to confirm in their terminal. If this agent has no interactive terminal, show the deletion summary and tell the user to rerun the displayed command directly; never bypass confirmation for them. ### End-to-end encryption If argument starts with "key generate" followed by an optional team name: 1. Run: `bash ~/.agents/skills/agmsg/scripts/key.sh generate []` 2. Show the full output to the user, including the mandatory key-backup notice. If argument starts with "key show": 1. Parse an optional team name and `--reveal-secret`. 2. Run: `bash ~/.agents/skills/agmsg/scripts/key.sh show [] [--reveal-secret]` 3. `--reveal-secret` requires a real interactive terminal and is refused in agent mode. Tell the user to run it directly in their own terminal. 4. Show the output to the user. If argument starts with "key handoff" followed by a team name: 1. Parse optional `--out ` and run: `bash ~/.agents/skills/agmsg/scripts/key.sh handoff [--out ]` 2. The output bundle contains every epoch identity and is itself permanent secret key material. Never read it into agent chat or display its contents. 3. Show the bundle path, latest snapshot digest, and full secrecy warning. If argument starts with "key import" followed by a team name: 1. Do not ask the user to paste the private identity into this chat, and do not run the command yourself. Tell the user to run this in their own terminal: ``` read -rsp 'Identity: ' IDENTITY; echo printf '%s' "$IDENTITY" | ~/.agents/skills/agmsg/scripts/key.sh import --identity-stdin unset IDENTITY ``` 2. Ask them to paste back only the command output, never the identity itself. 3. Do not offer an environment-variable path. An identity file is a permanent secret; always use the human-in-own-terminal flow above. If argument starts with "key rotate" followed by a team name: 1. Rotation mints a replacement epoch for a team that already has a key and announces it on the roster journal. It requires an existing current key, an identity journal (connect or migrate the team first), and `age`; it refuses with a message naming whichever is missing. 2. Confirm with the user before running it. It changes the team's key state, and every other machine has to receive the new identity out of band. 3. Run: `bash ~/.agents/skills/agmsg/scripts/key.sh rotate ` 4. Show the output: epoch, key_id, and recipient fingerprint. The private key is never written to the journal. Revealing it needs `key show --key-id --reveal-secret`, which is refused in agent mode — tell the user to run that in their own terminal. 5. Messages before the acknowledged rotation boundary remain readable with the old key. Device pairing (`key request` / `key approve`) is not implemented — they are not `key.sh` subcommands, so a call prints usage and exits 1. If the user asks for one, tell them so instead of attempting to run it. ## Permission prompts (Claude Code) Every agmsg step above runs through the host's Bash tool, so on Claude Code each call is gated by the permission system until you allowlist the script directory. Add these to `~/.claude/settings.json` (or project-level `.claude/settings.local.json`): ```json { "permissions": { "allow": [ "Bash(~/.agents/skills/agmsg/scripts/*)", "Bash(/Users//.agents/skills/agmsg/scripts/*)", "Bash(bash ~/.agents/skills/agmsg/scripts/*)", "Bash(bash /Users//.agents/skills/agmsg/scripts/*)" ] } } ``` Four entries rather than one because a rule matches the command string as written: the scripts are invoked both as `~/...` and as an absolute path, and with or without an explicit `bash` prefix. Replace `/Users/` with your home directory, and the `agmsg` path segment with your command name if you installed under a different one. **Every subcommand needs its own match.** [Claude Code's permission docs](https://code.claude.com/docs/en/permissions) state that a rule must match each subcommand independently, and that the recognized separators are `&&`, `||`, `;`, `|`, `|&`, `&`, and newlines. Chaining two agmsg scripts is fine — both match the entries above. What reintroduces the prompt is mixing in a command those entries do not cover: `delivery.sh status … ; printenv AGMSG_SPAWNED` prompts because of the `printenv`, not because of the `;`. Splitting it into its own call does not remove that prompt — it only keeps it from gating the agmsg call. Allowlist the command as well if it needs to be prompt-free. ## Sandbox compatibility (Claude Code) When Claude Code's sandbox is enabled, `watch.sh` (monitor mode) runs inside the sandbox and nee