2 Commits

Author	SHA1	Message	Date
Alejandro Gutiérrez	64ca600195	chore(cli): rename package to claudemesh-cli (unscoped) for npm publish ... @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>	2026-04-05 14:41:59 +01:00
Alejandro Gutiérrez	8931296e82	feat(cli): scaffold @claudemesh/cli MCP client package (stubs) ... The user-facing tool. Two invocation modes: - `claudemesh mcp` → MCP server (stdio), consumed by Claude Code - `claudemesh <subcommand>` → human CLI Layout: apps/cli/ ├── package.json bin: { claudemesh: ./src/index.ts } ├── README.md install + usage └── src/ ├── index.ts dispatcher (mcp | install | join | list | leave | --help) ├── env.ts CLAUDEMESH_BROKER_URL, CONFIG_DIR, DEBUG ├── mcp/ │ ├── server.ts MCP stdio server with 5 tools │ ├── tools.ts tool schemas (send_message, list_peers, │ │ check_messages, set_summary, set_status) │ └── types.ts ├── ws/client.ts broker connection (stub for 15b) ├── state/config.ts ~/.claudemesh/config.json (joined meshes + keys) └── commands/ ├── install.ts print `claude mcp add ...` instruction ├── join.ts parse ic://join/... (stub, Step 17) ├── list.ts show joined meshes └── leave.ts remove mesh from local config Tool stubs return "not connected, run `claudemesh join <invite-link>`" errors until 15b wires the WS client. Verified: - `bun src/index.ts --help` → prints usage - `bun src/index.ts install` → prints MCP add command with resolved path - `bun src/index.ts list` → "No meshes joined yet" - `bun src/index.ts mcp` (via stdin) → returns tools/list with all 5 tools Deps: @modelcontextprotocol/sdk, ws, libsodium-wrappers, zod. Lockfile regenerated in the same commit per claudemesh-3's flag — avoids breaking Coolify's --frozen-lockfile deploys. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-04 22:23:12 +01:00