@invariant.guru/cli 0.8.0 → 0.8.2

package/README.md

@@ -28,6 +28,22 @@ invariant session status <id> planning   # …and the agent reports back
 Those are ordinary shell commands. Any harness that can run one participates,
 and nothing here is coupled to any of them.
 
+## Loops: the graph above sessions
+
+Connect building, checks, independent review and acceptance with a portable loop:
+
+```bash
+invariant loop new --template feature --goal "Ship the export" --var 'check=yarn test'
+invariant loop start <loop-id>
+invariant loop next <loop-id>
+```
+
+Open **Loops** in the local UI to see the graph, recorded evidence and the next
+handoff. Each agent step gives you a session line to paste; human gates remain
+explicit. Files live in `.invariant/loops/`. Invariant never stages or commits.
+A loop works with one human and one agent on one laptop; a future server adds
+collaborators to these same files. See the [loop specification](docs/spec-loop.md).
+
 ## Where your work lives
 
 On your machine, in your repository:
@@ -731,8 +747,9 @@ invariant session                              # list
 invariant session next [<id>]                  # what to do now, and the command for it
 invariant session show <id> [--body]
 invariant session path <id>                    # the absolute path, alone
-invariant session status <id> <status> [--summary "…"] [--title "…"]
+invariant session status <id> <status> [--summary "…"] [--title "…"] [--harness codex]
 invariant session title <id> "A better title"
+invariant session harness <id> claude|codex|cursor # or --clear; status also detects the environment
 invariant session step list <id>
 invariant session step complete <id> 2         # …or part of the step's text, or --all
 invariant session write <id> --section Plan --file plan.md