Previous README documented 3 subcommands and got the completion shape
wrong (`completion generate`). Code has 6 top-level commands plus init,
totalling 22 subcommands.
Add a full command reference covering every subcommand in cmd tree:
- workspace: list, create, inspect, delete, restart, audit, delegate
- agent: list, inspect, send, peers
- platform: audit, health
- config: list, get, set, init, view
- connect: bridge external workspace (existing Quick Start)
- init: scaffold molecule.yaml
- completion: bash | zsh | fish | powershell (was: completion generate)
Each entry has a one-line purpose, key flags where applicable, and an
example. Also calls out `connect --mode push` (M4, not yet wired) and
the canvas-origin reply TODO in internal/connect/connect.go so users
know what isn't ready yet.
README-only change. No Go code edits.
The README still described molecule-cli as a "TUI dashboard" and used
the old `molecli` binary name. After M1 (RFC #10), the primary entry
point is `molecule connect <workspace-id>` — the out-of-box bridge
between an external-runtime workspace and a local agent backend.
Rewritten to:
- lead with the connect quick-start (token + API URL + invocation)
- document the three built-in backends (claude-code, exec, mock)
with --backend-opt examples
- list the flags external-workspace operators actually need
(--mode, --interval-ms, --since-secs, --dry-run)
- note the state-file location (cursor resume across restarts)
- link RFC #10 for the full design
- fix the binary name (`molecule`, not `molecli`)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
molecli — Go TUI dashboard for Molecule AI workspace monitoring.
Note: currently depends on platform Go packages; full API-only
decoupling tracked as follow-up.
