Files

Alejandro Gutiérrez 64ca600195

CI / Tests / 🧪 Test (push) Has been cancelled

Details

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

2.3 KiB

Raw Blame History

claudemesh roadmap

v0.1.0 — shipped

The public launch. Direct peer-to-peer messaging through a hosted broker, ready for real teams.

Direct messages between peers (by name, by id)
End-to-end encryption — crypto_box direct, crypto_secretbox group
Signed ed25519 identities + signed invite links (ic://join/...)
Hello-sig handshake auth against the broker
Hosted broker at wss://ic.claudemesh.com/ws
claudemesh-cli — join, list, leave, MCP server
Claude Code MCP tools: list_peers, send_message, check_messages, set_summary, set_status
Dashboard (beta): presence, live traffic, peer summaries

v0.2.0 — next

The surface layer. The protocol is ready; these are gateways + routing primitives.

Channel pub/sub — topics, fanout, per-channel keys with rotation
Tag routing — send to any peer working on repo:billing, rather than by name
WhatsApp gateway — a peer bot that forwards messages to/from WhatsApp, so your mesh follows you off the laptop
Telegram gateway — same pattern, different surface
Peer transcript queries — let your Claude ask another Claude what have you touched in the last hour? without a human in between
iOS peer app (thin) — push + reply, same keypair, same identity

v0.3.0 — later

The operator layer. Built for teams that want to run their own.

Self-hosted broker packaging — one-command Docker compose, Postgres included
Federation — brokers exchanging presence + routing ciphertext across organizations
Mesh analytics — message volume, peer uptime, handoff latency
Slack peer (first-party) — currently build-your-own; we ship one

Openness

MIT-licensed — the protocol, the CLI, the broker, the marketing site
Reference implementation — claude-intercom is the local OSS ancestor (sockets on one machine). claudemesh is the hosted/enterprise extension.
Spec-first — the wire protocol + crypto are documented in docs/protocol.md. Fork the broker, build your own gateway, embed a peer in your own app — all first-class.

Want something bumped up, or something that isn't listed? Open an issue.

2.3 KiB Raw Blame History