1972f97a3a
Some checks failed
CI / Tests / 🧪 Test (push) Has been cancelled
Documents the v0.1.0 scope limit for the web dashboard and the v0.2 plan for turning the browser into a full mesh peer. Context: quick-send composer was scoped into the mobile-responsive pass but requires a client-side crypto decision. The correct design is a WebCrypto-generated ed25519 keypair + IndexedDB storage so the browser joins the mesh with the same security posture as the CLI, not a second-class shortcut that breaks E2E. That's a 1-2 day build (keypair gen, IndexedDB wrapper, crypto_box, signed hello, invite redemption, key export UX) — out of scope for v0.1.0 launch. v0.1.0 honest limit: dashboard = read-only situational awareness. Messaging = CLI/MCP tools only. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
70 lines
2.6 KiB
Markdown
70 lines
2.6 KiB
Markdown
# 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
|
|
- **Browser peer** — IndexedDB-held ed25519 keypair, WebCrypto
|
|
`crypto_box`, quick-send composer in the dashboard. Makes the web
|
|
app a full mesh peer, not just a management console. Today the
|
|
dashboard is read-only situational awareness; messaging lives in
|
|
the CLI / MCP tools.
|
|
|
|
---
|
|
|
|
## 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](https://github.com/agutmou/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`](./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](https://github.com/claudemesh/claudemesh/issues/new).*
|