GeojoL

Agents Msger — AI skill for Claude Code

AI community

Cross-machine, cross-network message passing between AI coding-agent sessions — connect context, talk, and reach the agent responsible for a project.

How to install Agents Msger

This entry records only its repository, not the path inside it, so there is no exact command to give. Open GeojoL/agents-msger and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agents Msger does

Cross-machine, cross-network message passing between AI coding-agent sessions — connect context, talk, and reach the agent responsible for a project. Built on Claude Code's own cross-session messaging, exposed as MCP tools.

Alternatives in AI

Cursor Talk To Figma MCP — TalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to c 7k ★
Agmsg — Cross-vendor messaging for CLI AI coding agents — let Claude Code, Codex, Gemini & Copilot talk to each other 1.5k ★
DontFeedTheAI — Transparent anonymization proxy for AI-assisted pentesting 654 ★

README

agents-msger

**A shared line for AI agents — connect context, talk to each other, and reach whoever owns a project. Across machines, across networks.**

[![license](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE) [![python](https://img.shields.io/badge/python-3.8%2B-blue.svg)](#requirements) [![python deps](https://img.shields.io/badge/python%20deps-none%20(stdlib)-brightgreen.svg)](#requirements) [![requires](https://img.shields.io/badge/requires-Claude%20Code-blueviolet.svg)](#requirements) [![status](https://img.shields.io/badge/status-early%20preview-orange.svg)](#project-status) [![agents](https://img.shields.io/badge/agents-Claude%20Code-blueviolet.svg)](#supported-agents)

The problem

Claude Code already has **cross-session messaging**: sessions on the *same machine* can deliver messages to each other through Claude Code's own messaging socket. But that stops at the edge of one machine. The moment your agents live on different machines — or on different networks — there is no path between them: no way to hand context across, no way to ask and get an answer back, and no way to reach *the* agent that owns a project running somewhere else.

**`agents-msger` extends Claude Code's own messaging across machines and networks.** It does not reinvent agent messaging — it reuses Claude Code's native cross-session delivery and adds the one missing piece: a hub + per-machine shim that carries those same messages between machines, over any network that can reach the hub.

What it does

🔗 Connect context. Any agent session can send its context — a summary, a decision, a hand-off — directly into another agent's session, on the same machine or a different one. The receiving agent picks it up on its next turn.
💬 Communicate. Every delivered message carries who sent it — persona, machine, window, and pid. So a back-and-forth is natural: the recipient knows exactly which agent (and which session) t