clawborrator-cli 0.0.59 → 0.2.0

package/README.md

@@ -200,10 +200,9 @@ claw logout                                    # revokes the session token + cle
 
 ## `claw session attach` — the TUI
 
-This is the killer feature. Three or more humans attached to the
-same Claude Code session, seeing each other's prompts in real time,
-racing on tool-permission approvals, talking to each other in a side
-channel that doesn't pollute Claude's context.
+Multiple operators attach to the same Claude Code session, see each
+other's prompts in real time, race on tool-permission approvals, and
+chat in a side channel that stays out of Claude's context.
 
 ```
 $ claw session attach @backend
@@ -276,15 +275,16 @@ peer.
 ## Where to look next
 
 - **Hub home & demos:** <https://next.clawborrator.com/>
-- **REST API (OpenAPI):** <https://next.clawborrator.com/docs>
-- **WebSocket (AsyncAPI):** <https://next.clawborrator.com/ws-docs>
+- **REST API (OpenAPI):** <https://next.clawborrator.com/api/http-docs>
+- **WebSocket (AsyncAPI):** <https://next.clawborrator.com/api/ws-docs>
 - **Webhook reference:** <https://next.clawborrator.com/demos/webhooks/>
 - **A2A bridge reference:** <https://next.clawborrator.com/demos/a2a-docs/>
-- **Source / issues / contributing:** <https://github.com/clawborrator/hub_v1>
+- **CLI source / issues:** <https://github.com/clawborrator/cli_v1>
+- **Hub source:** <https://github.com/clawborrator/hub_v1>
 
-The CLI source is in `cli/` of the same repo; it's a thin shell over
-the REST + WS surface, so anything `claw` does you can do directly
-from any HTTP client.
+The CLI is a thin shell over the hub's REST + WebSocket surface — anything
+`claw` does you can do directly from any HTTP client. Wire types live in
+`src/shared/` (vendored from the hub repo's `shared/` workspace).
 
 ---