claude-chatter
Claude Code peer messaging protocol and client library.
claude-chatter provides a standalone Python implementation of the Claude Code peer-to-peer messaging protocol. It handles peer discovery via local session descriptors (~/.claude/sessions/*.json), background jobs inspection (~/.claude/jobs), UNIX domain socket IPC, NDJSON message framing, and local SQLite mailbox persistence.
This library has no dependencies on FastMCP or Antigravity and can be used directly in any Python application or CLI workflow.
Installation
pip install claude-chatter
Messaging tools
The library implements the peer messaging tools that Claude Code exposes to its own agents (SendMessage and ListAgents), so any Python program can act as a peer:
ClaudeClient.send_message(target_session, message_content, priority="next")delivers a message to a live session over its UNIX socket. The target is resolved by name, PID, session id or a partial name match.ClaudeClient.list_sessions()returns the live sessions found in~/.claude/sessions, with peer tokens redacted unlessredact_tokens=False.ClaudeWire.scan_sessions()does the same without a client.
Received messages are stored in the local mailbox and read with get_unread_messages() and get_history(). The CLI equivalents are --send, --list, --inbox and --history.
Quick Start
As a Library
import asyncio
from claude_chatter import ClaudeClient, ClaudeWire
async def main():
# Stateless discovery
sessions = ClaudeWire.scan_sessions()
print("Discovered sessions:", sessions)
# Initialize client node
client = ClaudeClient(session_name="my-worker")
# Send message to an active session
res = await client.send_message(
target_session="other-session",
message_content="Hello from claude-chatter"
)
print("Send status:", res)
if __name__ == "__main__":
asyncio.run(main())
Inbound Message Callback
async def on_message(event):
print(f"Received frame {event['msg_id']} from {event['sender']}: {event['content']}")
client = ClaudeClient(session_name="listener", on_inbound_message=on_message)
An inbound {"type":"auth","token":"..."} line (peerToken is accepted as the key too) is checked against the token this process registered, and the connection is closed on a mismatch. ClaudeClient(require_auth=True) additionally refuses any connection that does not open with a valid auth line.
On send, when the target's key file provides a token, the connection opens with {"type":"auth","token":"..."} before the message frame. A Claude Code session (checked on Linux, 2.1.325) delivers a message whether or not the line is present and whatever token it carries.
await client.notify_when_idle(target, timeout=None) subscribes to a one-shot notice for when a Claude Code session next goes idle (Claude Code v2.1.236 or later, same machine) and returns it as {"success": True, "notice": {...}}. The notice is sent to this client's reply socket, so a listener must be bound (start_bridge_listener); without one the call fails. Control frames other than the idle notice are logged and not stored as messages.
event["sender"] is the live session that owns the connecting process (or an ancestor of it) when one can be found, with event["sender_verified"] = True. Otherwise it is the name the frame claims and sender_verified is False. claimed_sender, peer_pid and the wrapper's from_mode are always included. Peer lookup needs Linux (SO_PEERCRED) and a sender that is still running when the connection is accepted.
CLI Tool
The package installs both claude-chatter and chatter CLI entry points:
# List all active Claude Code sessions
claude-chatter --list
# List Claude Code background jobs
claude-chatter --jobs
# Inspect unread messages from local mailbox
claude-chatter --inbox
# View full persisted message history
claude-chatter --history
# Send message to a target session
claude-chatter --send target-session "Hello peer"
# Run standalone daemon socket listener
claude-chatter --standalone --name my-daemon
# Proactively scan and purge dead session files
claude-chatter --purge
Provenance
claude-chatter was extracted from non7top/claude-chatter-mcp to provide a reusable, host-independent library for the Claude Code peer messaging protocol with zero MCP dependencies. Full commit history of the protocol core was preserved during the separation.
License
MIT
Metadata
Release files for claude-chatter 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| claude_chatter-0.3.0.tar.gz | 46.4 kB | With provenance | Details for claude_chatter-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| claude_chatter-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for claude_chatter-0.3.0-py3-none-any.whl |
Total release size: 75.1 kB
Release files / claude_chatter-0.3.0.tar.gz
| Download URL | claude_chatter-0.3.0.tar.gz |
|---|---|
| Size | 46.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d1589ec91a596772735815445eab0e50f05212b0a67c2eb02e288d63b558e8a
|
|
BLAKE2b-256 checksum How to use checksums |
4e8a186b8628cd0bce057805b9878e068ced5af46e21015b7bb34b6bb2b5a260
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / claude_chatter-0.3.0-py3-none-any.whl
| Download URL | claude_chatter-0.3.0-py3-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f652ead9df7cf5a6c2ea739dd3318237e5d2f3d637b0c9f93a9b8d481fef0b9
|
|
BLAKE2b-256 checksum How to use checksums |
53a99a698f2d88853945c5abe8e4bdf680a79696ffe410390594c99bd2029ef0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for claude-chatter 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for claude_chatter-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.