claudemesh-cli 1.5.0 → 1.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -2
- package/dist/entrypoints/cli.js +1317 -7
- package/dist/entrypoints/cli.js.map +15 -8
- package/dist/entrypoints/mcp.js +155 -2
- package/dist/entrypoints/mcp.js.map +3 -3
- package/package.json +2 -1
- package/skills/claudemesh/SKILL.md +25 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claudemesh-cli",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.6.0",
|
|
4
4
|
"description": "Peer mesh for Claude Code sessions — CLI + MCP server.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"claude-code",
|
|
@@ -55,6 +55,7 @@
|
|
|
55
55
|
"zod": "4.1.13"
|
|
56
56
|
},
|
|
57
57
|
"devDependencies": {
|
|
58
|
+
"@claudemesh/sdk": "workspace:*",
|
|
58
59
|
"@turbostarter/eslint-config": "workspace:*",
|
|
59
60
|
"@turbostarter/prettier-config": "workspace:*",
|
|
60
61
|
"@turbostarter/tsconfig": "workspace:*",
|
|
@@ -36,6 +36,31 @@ Every broker-touching verb runs through a policy gate before dispatch. The defau
|
|
|
36
36
|
|
|
37
37
|
**Convention:** every operation is `claudemesh <resource> <verb>`. Legacy short forms (`send`, `peers`, `kick`, `remember`, ...) are aliases that keep working forever; prefer the resource form for new code.
|
|
38
38
|
|
|
39
|
+
### `topic` — conversation scope within a mesh (v0.2.0)
|
|
40
|
+
|
|
41
|
+
A topic is a named conversation inside a mesh. Mesh = trust boundary. Group = identity tag. **Topic = what you're talking about.** Subscribers receive topic-tagged messages; non-subscribers don't. Topics also persist message history so humans (and opting-in agents) can fetch back-scroll on reconnect.
|
|
42
|
+
|
|
43
|
+
```bash
|
|
44
|
+
claudemesh topic create deploys --description "deploy + on-call"
|
|
45
|
+
claudemesh topic create incident-2026-05-02 --visibility private
|
|
46
|
+
claudemesh topic list # all topics in mesh
|
|
47
|
+
claudemesh topic join deploys # subscribe (by name or id)
|
|
48
|
+
claudemesh topic join deploys --role lead # join as lead
|
|
49
|
+
claudemesh topic leave deploys
|
|
50
|
+
claudemesh topic members deploys # list subscribers
|
|
51
|
+
claudemesh topic history deploys --limit 50 # fetch back-scroll
|
|
52
|
+
claudemesh topic history deploys --before <msg-id> # paginate older
|
|
53
|
+
claudemesh topic read deploys # mark all as read
|
|
54
|
+
|
|
55
|
+
# Send to a topic — same `send` verb, target starts with #
|
|
56
|
+
claudemesh send "#deploys" "rolling out 1.5.1 to staging"
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
When to use topics vs groups vs DM:
|
|
60
|
+
- **DM** (`send <peer>`) — 1:1, ephemeral.
|
|
61
|
+
- **Group** (`send "@frontend"`) — addresses everyone in a group; ephemeral; for coordinating teams.
|
|
62
|
+
- **Topic** (`send "#deploys"`) — durable conversation room; for ongoing work threads, incident channels, build-status feeds.
|
|
63
|
+
|
|
39
64
|
### `peer` — read connected peers + admin (kick / ban / verify)
|
|
40
65
|
|
|
41
66
|
```bash
|