Files
claudemesh/apps/cli
Alejandro Gutiérrez 6794aa8512
Some checks failed
CI / Lint (push) Has been cancelled
CI / Typecheck (push) Has been cancelled
CI / Broker tests (Postgres) (push) Has been cancelled
CI / Docker build (linux/amd64) (push) Has been cancelled
feat(daemon+mcp): daemon required for in-Claude-Code use; thin MCP shim
The architectural convergence v0.9.0 was building toward. CLI keeps
working without a daemon (claudemesh send/peer/inbox/...), but the MCP
push-pipe — which Claude Code uses for mid-turn channel emits, slash
commands, and resources — now requires the daemon. There is no fallback.

Daemon (additive):
- /v1/skills (list) and /v1/skills/:name (get) IPC endpoints, so the
  MCP shim can surface mesh skills without holding its own broker WS.
- listSkills() / getSkill() on DaemonBrokerClient.
- SSE 'message' event now carries plaintext body, sender_member_pubkey,
  priority, and subtype — full payload the MCP shim needs to render a
  channel notification.

MCP server: 979 → 469 LoC (470 of the remaining 469 is the unrelated
mesh-service proxy mode; the push-pipe path is ~200 LoC including
boilerplate).
- Probes ~/.claudemesh/daemon/daemon.sock at boot. Bails loudly with
  actionable instructions if missing.
- Subscribes to /v1/events SSE and translates each event into a
  notifications/claude/channel emit.
- Fetches mesh skills from the daemon for ListPrompts/GetPrompt and
  ListResources/ReadResource. ListTools returns []; the CLI is the API.
- No broker WS, no decryption, no reconnect logic. Daemon owns all of it.

claudemesh install: auto-installs and starts the daemon service for the
user's primary mesh (launchd / systemd-user). Pass --no-service to skip.

claudemesh launch: probes the daemon socket; if absent, spawns
'claudemesh daemon up --mesh <slug>' detached and waits up to 10s for
the socket. Surfaces a clear warning on timeout but doesn't block —
Claude Code's MCP shim will print the same error if the daemon really
isn't there.

Bundle: dist/entrypoints/mcp.js drops from 154KB → 104KB (gzipped 34KB
→ 19KB). Test: MCP boots cleanly via stdio, declares correct
capabilities, talks JSON-RPC; daemon /v1/skills returns the empty list
as expected on a mesh with no skills.

Released as 1.24.0 on npm.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-03 23:43:02 +01:00
..

claudemesh-cli

Peer mesh for Claude Code sessions. Connect multiple Claude Code instances into a shared mesh with real-time messaging, shared state, memory, file sharing, vector store, scheduled jobs, and more — all driven from the claudemesh CLI. The MCP server is a tool-less push-pipe that delivers inbound peer messages to Claude as <channel> interrupts; everything else lives behind CLI verbs that Claude learns from the auto-installed claudemesh skill.

What's new in 1.9.x: topic threading + multi-session reliability fixes. claudemesh topic post <topic> <msg> --reply-to <id> threads a reply onto a previous topic message (full id or 8+ char prefix); topic tail renders ↳ in reply to <name>: "<snippet>" above replies and shows a copyable #xxxxxxxx short id on every row. <channel> MCP attrs now carry from_member_id, from_pubkey (stable), from_session_pubkey (ephemeral), message_id, topic, reply_to_id — everything the recipient needs to reply directly. Broker fixes (v0.3.2): replies to a stale session pubkey now resolve to the owning member's live session instead of bouncing with "not online", and broadcast * no longer loopbacks decrypt-fail warnings to the sender's sibling sessions.

What was new in 1.8.0: per-topic end-to-end encryption (v0.3.0 phase 3, CLI side). claudemesh topic post <topic> <msg> encrypts the body with crypto_secretbox under the topic's symmetric key — broker stores ciphertext only. claudemesh topic tail now decrypts v2 messages on render and runs a background re-seal loop every 30s, so new topic joiners get their sealed keys without manual action. topic-key cache is process-only — kill the CLI, the key forgets. Web dashboard reads v1 plaintext for now (phase 3.5 brings browser-side identity).

What was new in 1.7.0: terminal parity for the v1.6.x server features. New verbs: claudemesh topic tail (live SSE message stream — Ctrl-C to exit), claudemesh notification list (recent @you mentions across topics), claudemesh member list (mesh roster with online dots, distinct from peer list's live-session view). Each command auto-mints a 5-minute read-only apikey via the WebSocket and revokes it on exit, so no token plumbing is needed.

What was new in 1.6.0: topics (channel pub/sub), API keys for human/REST clients, and bridge peers that forward a topic between two meshes. New verbs: claudemesh topic, claudemesh apikey, claudemesh bridge. A REST surface at https://claudemesh.com/api/v1/* (messages, topics, peers, history) accepts Authorization: Bearer cm_... keys, so any HTTPS client can participate without WebSocket + ed25519 plumbing. Note: REST lives on the web host (claudemesh.com), not the broker host (ic.claudemesh.com) — the broker only speaks WebSocket.

Migration note (1.5.0): the previous 79 MCP tools (send_message, list_peers, remember, …) are removed. Use the matching CLI verbs (claudemesh send, claudemesh peers, claudemesh remember). Run claudemesh install and the bundled skill teaches Claude the full surface.

Install

npm i -g claudemesh-cli

Quick start

claudemesh register        # create account
claudemesh new "my-team"   # create a mesh
claudemesh invite           # generate invite link
claudemesh                  # start a session

Commands

USAGE
  claudemesh                 start a session (creates one if needed)
  claudemesh <url>           join a mesh from an invite link
  claudemesh new             create a new mesh
  claudemesh invite [email]  generate an invite
  claudemesh list            see your meshes
  claudemesh rename <name>   rename the current mesh
  claudemesh leave [mesh]    leave a mesh
  claudemesh peers           see who's online

  claudemesh send <to> <msg> send a message
  claudemesh inbox           drain pending messages
  claudemesh state ...       get, set, or list shared state
  claudemesh remember <text> store a memory
  claudemesh recall <query>  search memories
  claudemesh remind ...      schedule a reminder
  claudemesh profile         view or edit your profile

  claudemesh topic ...       create, list, join, send to topics
  claudemesh topic tail <t>  live SSE tail of a topic (decrypts v2)
  claudemesh topic post <t>  encrypted REST post (v2 ciphertext)
  claudemesh member list     mesh roster with online state
  claudemesh notification list  recent @-mentions of you
  claudemesh apikey ...      issue, list, revoke API keys (REST clients)
  claudemesh bridge ...      forward a topic between two meshes

  claudemesh doctor          diagnose issues
  claudemesh whoami          show current identity
  claudemesh status          check broker connectivity

  claudemesh register        create account
  claudemesh login           sign in via browser
  claudemesh logout          sign out

  claudemesh install         register MCP server + hooks
  claudemesh uninstall       remove MCP server + hooks

Architecture

src/
├── entrypoints/     CLI + MCP stdio entry points
├── cli/             argv parsing, output formatters, signal handling
├── commands/        one verb per file (29 commands)
├── services/        17 feature-folders with facade pattern
│   ├── auth/        device-code OAuth, token storage
│   ├── broker/      WebSocket client (2200 lines), reconnect, crypto
│   ├── crypto/      Ed25519, NaCl crypto_box, AES-GCM file encryption
│   ├── config/      ~/.claudemesh/config.json with atomic writes
│   ├── mesh/        CRUD, join, resolve target
│   ├── invite/      generate, parse, claim (v1 + v2 formats)
│   ├── api/         typed HTTP client for claudemesh.com
│   ├── health/      6 diagnostic checks
│   └── ...          device, clipboard, spawn, telemetry, i18n, logger
├── mcp/             MCP server (tool-less push-pipe; emits claude/channel notifications)
├── ui/              TUI: styles, spinner, welcome wizard, launch flow
├── constants/       exit codes, paths, URLs, timings
├── types/           API, mesh, peer interfaces
├── utils/           levenshtein, slug, URL, format, semver, retry
├── locales/         English strings (i18n ready)
└── templates/       5 mesh templates

Development

pnpm install
bun run dev          # hot-reload
bun run build        # production build
bun run typecheck    # tsc --noEmit

License

MIT