sini

Xmsg — Development skill for Claude Code

Development community

Bridge into running Claude Code, Antigravity and pi agent sessions.

How to install Xmsg

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

What Xmsg does

Bridge into running Claude Code, Antigravity and pi agent sessions.

Alternatives in Development

  • Agy2api — 将 Antigravity 转换为 OpenAI 、GEMINI 和 Claude API 接口 5.3k ★
  • Claude SEO — Multi-Platform Agent Instructions — For Cursor, Cursor Cloud Agents, Google Antigravity, and Gemini CLI 5k ★
  • Gcli2api — 将 GeminiCLI 和 Antigravity 转换为 OpenAI 、GEMINI 和 Claude API 接口 4.6k ★

README

xmsg: Local Inter-Agent Messaging & Coordination Bridge

`xmsg` is a fast, lightweight local messaging bridge connecting running AI agent sessions across harnesses (Claude Code, Antigravity, and Pi) on the local host. It provides direct, zero-overhead inbox delivery, attested caller identification, persistent reply threading, and MCP tooling.


1. Security Architecture & Trust Model

1.1 Same-UID Trust Boundary

All local IPC in `xmsg` relies on Unix domain sockets located in `$XDG_RUNTIME_DIR/xmsg/` (mode `0700` directory, socket mode `0600`, owned by the running user's UID):

  • Sockets authenticate connected peers via kernel-attested credentials (SO_PEERCRED UID).
  • Any process executing under the same local UID is within the trust boundary and may connect to the Unix sockets.
  • Sockets are protected against symlink attacks and race conditions on startup by verifying directory ownership and permissions prior to binding.

1.2 No-Authentication HTTP Posture

[!WARNING] **No-Auth HTTP Service**: The `xmsg` HTTP server provides **no authentication mechanisms**. It is designed solely for local inter-process communication and **MUST STRICTLY bind to the loopback interface (`127.0.0.1`)**. Never expose the HTTP port to external networks, shared interfaces, or container bridges without a dedicated authenticating proxy.

1.3 Attestation & Identity Derivation

`xmsg` prevents cross-session and cross-harness impersonation among non-adversarial same-UID processes:

  • Claude Sessions: Discovered via ~/.claude/sessions and verified for process liveness and starttime continuity via /proc//stat.
  • Antigravity Sessions: Verified via presence lock holder files in /proc/locks (enforcing FLOCK only and refusing ambiguous multiple holders).
  • Pi Sessions: Session identity is server-derived from attested kernel process parameters:
    sessionId = "pi:" || peer_pid || ":" || starttime
    Caller-asserted session IDs in r