Files

Alejandro Gutiérrez f34b8fbc6b docs(cli): improve --help text for clarity, concision, and consistency

Rewrite all command and argument descriptions in index.ts to follow
imperative mood, omit filler, use backtick-formatted values, and
surface key behaviors (e.g. launch spawns Claude Code with MCP,
remind supports list/cancel subactions, send accepts @group and *).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-07 23:31:55 +01:00

scripts

feat(broker): invite signature verification + atomic one-time-use

2026-04-04 23:02:12 +01:00

src

docs(cli): improve --help text for clarity, concision, and consistency

2026-04-07 23:31:55 +01:00

eslint.config.js

feat(cli): scaffold @claudemesh/cli MCP client package (stubs)

2026-04-04 22:23:12 +01:00

package.json

chore: bump cli to 0.6.8

2026-04-07 22:39:21 +01:00

README.md

feat(cli): claudemesh launch command with transparency banner (v0.1.2)

2026-04-05 22:22:46 +01:00

tsconfig.json

feat(cli): scaffold @claudemesh/cli MCP client package (stubs)

2026-04-04 22:23:12 +01:00

vitest.config.ts

test(cli): add crypto roundtrip and invite parse tests

2026-04-06 00:18:27 +01:00

README.md

claudemesh-cli

Client tool for claudemesh — install once per machine, join one or more meshes, and your Claude Code sessions can talk to peers on demand.

Install

# From npm (once published)
npm install -g claudemesh-cli

# Or from the monorepo during dev
cd apps/cli && bun link

Then register the MCP server with Claude Code:

claudemesh install
# prints:  claude mcp add claudemesh --scope user -- claudemesh mcp

Run the printed command, then restart Claude Code.

Join a mesh

claudemesh join https://claudemesh.com/join/<token>

Launch Claude Code

For real-time push messages from peers (messages injected mid-turn as <channel source="claudemesh"> system reminders), launch with:

claudemesh launch
# or pass through any claude flags:
claudemesh launch --model opus
claudemesh launch --resume

Under the hood this runs:

claude --dangerously-load-development-channels server:claudemesh

Plain claude still works — the MCP tools are available — but incoming messages are pull-only via the check_messages tool instead of being pushed to Claude immediately.

The invite link is generated by whoever runs the mesh. It bundles the mesh id, expiry, signing key, and role. Your CLI verifies it, generates a fresh keypair, enrolls you with the broker, and persists the result to ~/.claudemesh/config.json.

Commands

claudemesh install         # register MCP + status hooks
claudemesh uninstall       # remove MCP + status hooks
claudemesh launch [args]   # launch Claude Code with push messages enabled
claudemesh join <url>      # join a mesh via invite URL
claudemesh list            # show joined meshes + identities
claudemesh leave <slug>    # leave a mesh
claudemesh mcp             # start MCP server (stdio — Claude Code only)
claudemesh --help          # show usage

Env overrides

Var	Default	Purpose
`CLAUDEMESH_BROKER_URL`	`wss://ic.claudemesh.com/ws`	Point at a self-hosted broker
`CLAUDEMESH_CONFIG_DIR`	`~/.claudemesh/`	Override config location
`CLAUDEMESH_DEBUG`	`0`	Verbose logging

Status

v0.1.0 scaffold — CLI commands + MCP server shell in place. WS broker connection, libsodium crypto, invite-link verification, and auto-install of hooks land in subsequent steps.