64ca600195
Some checks failed
CI / Tests / 🧪 Test (push) Has been cancelled
@claudemesh/cli was already taken on npm by an unrelated project
(claudemesh "domain packages", v1.0.7). PM picked option A: publish
unscoped as claudemesh-cli. Binary name stays "claudemesh" — users
type the natural thing on install:
npm install -g claudemesh-cli
claudemesh install
claudemesh join ic://join/...
renamed references everywhere:
- apps/cli/package.json: name
- apps/cli/README.md: title + install command
- apps/cli/src/{index.ts, mcp/server.ts, commands/install.ts} headers
- docs/QUICKSTART.md: install command, version banner, npx hint
- docs/roadmap.md: package name
also (PM journey-friction #5): surface the "restart Claude Code" step
LOUDLY in install output. Added a yellow-bold warning line after the
✓ success lines so new users don't miss the restart step (MCP tools
only load on Claude Code restart).
⚠ RESTART CLAUDE CODE for MCP tools to appear.
ANSI colors gated on isTTY + NO_COLOR/TERM=dumb guards.
bundle rebuilt. ready for npm publish pending user's `npm adduser`.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
60 lines
1.8 KiB
Markdown
60 lines
1.8 KiB
Markdown
# 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
|
|
|
|
```sh
|
|
# 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:
|
|
|
|
```sh
|
|
claudemesh install
|
|
# prints: claude mcp add claudemesh --scope user -- claudemesh mcp
|
|
```
|
|
|
|
Run the printed command, then restart Claude Code.
|
|
|
|
## Join a mesh
|
|
|
|
```sh
|
|
claudemesh join ic://join/BASE64URL...
|
|
```
|
|
|
|
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
|
|
|
|
```sh
|
|
claudemesh install # print MCP registration command
|
|
claudemesh join <link> # join a mesh via invite link
|
|
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.
|