@staff0rd/assist 0.708.2 → 0.710.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 CHANGED
@@ -203,7 +203,7 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
203
203
  - `assist backlog rewind <id> <phase> --reason <reason>` - Rewind an item to an earlier phase
204
204
  - `assist backlog next [id] [--once]` - Pick and run the next backlog item, or open `/draft` if none remain
205
205
  - `assist backlog refine [id] [--once] [--harness <claude|codex|pi>]` - Alias for `refine`
206
- - `assist backlog run <id> [--harness <claude|codex|pi>] [--write|--no-write]` - Run a backlog item's plan phase-by-phase with the selected harness, defaulting to `harness.engine`; for Codex, write access uses the `workspace-write` sandbox and `--no-write` uses `read-only`. Each phase prompt scopes the agent to the item's own repo: it must ask before modifying, committing or pushing any other repo
206
+ - `assist backlog run <id> [--harness <claude|codex|pi>] [--write|--no-write]` - Run a backlog item's plan phase-by-phase with the selected harness, defaulting to `harness.engine`; for Codex, write access uses the `workspace-write` sandbox and `--no-write` uses `read-only`. Each phase prompt scopes the agent to the item's own repo: it must ask before modifying, committing or pushing any other repo. Set `backlog.crossRepo` to `true` to lift this limit (and the matching `/draft`/`/refine` rule) for repos whose items span other repos
207
207
  - `assist backlog export [file]` - Export every table in the backlog database to a file, or stdout
208
208
  - `assist backlog import [file]` - Restore every table present in a dump back into the database (`-y, --yes` skips the prompt)
209
209
  - `assist backlog associate-jira <id> [key]` - Associate a Jira ticket (bare key or browse URL); clears any GitHub issue on the item. `--clear` removes it
@@ -389,9 +389,11 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
389
389
  - `assist sessions nodes [--json]` - List this node and every linked node with its link state (see [Linked nodes](#linked-nodes))
390
390
  - `assist sessions nodes link <name> <url>` - Link a peer node by its web server URL
391
391
  - `assist sessions nodes unlink <name>` - Remove a linked node
392
+ - `assist sessions nodes doctor [name] [--json]` - Probe each hop of every link (or one) and stop at the first failure with a remediation
393
+ - `assist sessions nodes logs <name> [-n, --lines <count>] [--json]` - Tail a linked node's `daemon.log` through its web server
392
394
  - `assist sessions set-status <status>` - Report the current session's status (`running`/`waiting`) to the daemon; invoked by the Claude Code hooks the daemon wires into each session
393
395
  - `assist daemon run` - Run the sessions daemon in the foreground (normally auto-spawned detached)
394
- - `assist daemon status` - Show daemon status, live sessions, and any stray processes or stolen socket
396
+ - `assist daemon status` - Show daemon status, live sessions, each link's state, and any stray processes or stolen socket
395
397
  - `assist daemon stop` - Stop the sessions daemon; running claude sessions resume on next start
396
398
  - `assist daemon restart` - Restart the sessions daemon, resuming previously running claude sessions
397
399
  - `assist daemon drain [--yes]` - Remove all sessions from the local daemon for a clean slate; a session holding unpushed work is stopped, not removed
@@ -426,9 +428,11 @@ Each assist install is a **node** with its own daemon and web server. A node can
426
428
  - `assist sessions nodes [--json]` — this node and each link's state (connected / connecting / disconnected / version-blocked), peer version and last error.
427
429
  - `assist sessions nodes link <name> <url>` — link a peer by its web server URL, e.g. `assist sessions nodes link <name> http://127.0.0.1:<port>`. `<name>` must match the peer's `sessions.nodeName`. A running daemon picks up the change immediately.
428
430
  - `assist sessions nodes unlink <name>` — remove a link.
431
+ - `assist sessions nodes doctor [name] [--json]` — probes each link's hops in order: the peer's web server (`GET /api/health`, including that its `nodeName` matches the link), the peer's daemon (as its health reports it), a WebSocket `hello` (version and protocol), then this node's own link state. It stops at the first failing hop and prints the raw error with a remediation, and exits 1 on any failure. On WSL with no links, it reports a Windows node answering on `127.0.0.1:3101` and prints the command that links it.
432
+ - `assist sessions nodes logs <name> [-n, --lines <count>] [--json]` — tail a linked node's `daemon.log` (default 200 lines) through its web server's `GET /api/daemon-log`; naming this node reads the local log.
429
433
  - `sessions.linkVersionCheck` — reaction to a version mismatch with a linked node: `block` (default) heals an older peer by calling its `POST /api/self-update` (runs `assist update`, then restarts its daemon and web server) and reconnects, latching with an error if the gap remains or this node is the older side; `warn` proceeds anyway; `off` skips the check.
430
434
 
431
- With more than one node, a machine picker appears in the top nav and a machine selector in the new-session dialog; the dialog's selector defaults to the top nav's choice, which is remembered per browser. Linked nodes' daemon lines appear in this node's `daemon.log` tagged `[<node>]`. The retired `sessions.windows*` keys are ignored.
435
+ With more than one node, a machine picker appears in the top nav and a machine selector in the new-session dialog; the dialog's selector defaults to the top nav's choice, which is remembered per browser. Linked nodes' daemon lines appear in this node's `daemon.log` tagged `[<node>]`. Every launch forwarded over a link and every `?node=` panel request carries a `traceId`, logged as `trace=<id>` by both nodes. `GET /api/health` reports the node's name, version, protocol, daemon reachability and its links' states. The retired `sessions.windows*` keys are ignored.
432
436
 
433
437
  ### Session config keys
434
438
 
package/allowed.cli-reads CHANGED
@@ -61,6 +61,8 @@ assist screenshot
61
61
  assist seq auth list
62
62
  assist seq query
63
63
  assist sessions nodes
64
+ assist sessions nodes doctor
65
+ assist sessions nodes logs
64
66
  assist sql auth list
65
67
  assist sql columns
66
68
  assist sql query
@@ -79,7 +79,7 @@ Two tests for each phase before proposing the plan:
79
79
  1. **Observable**: can you answer "does this work?" by running or inspecting the result? If a phase only produces internal plumbing with no observable effect, it's horizontal — restructure it.
80
80
  2. **Self-contained**: would `assist verify` pass with only this phase's code committed — no unused exports, no dead stubs awaiting a later phase? If not, merge the producer and its consumer into the same phase.
81
81
 
82
- **Every task stays in this repo.** An item belongs to the repo whose backlog it is in, and phase runs work only there. Never plan a task that edits, commits or pushes another repo (e.g. "In ~/git/other-repo, change..."). If the idea needs changes in another repo, leave that work out of the plan and tell the user to file it as a separate item in that repo's backlog.
82
+ **Every task stays in this repo** unless `assist config get backlog.crossRepo` prints `true`. An item belongs to the repo whose backlog it is in, and phase runs work only there. Never plan a task that edits, commits or pushes another repo (e.g. "In ~/git/other-repo, change..."). If the idea needs changes in another repo, leave that work out of the plan and ask the user to file it as a separate item in that repo's backlog.
83
83
 
84
84
  Keep phases small (2-4 tasks each). A typical item should have 2-3 phases.
85
85
 
@@ -79,7 +79,7 @@ When adding or restructuring plan phases, follow the same rules as /draft:
79
79
 
80
80
  - **Vertical slices, not horizontal layers.** Each phase delivers a thin, working increment verifiable end-to-end — never "backend in phase 1, UI in phase 2".
81
81
  - **Every phase must pass `assist verify` on its own.** Verification includes knip, which fails on unused exports — so every export a phase adds must have a caller wired up in that same phase. No "phase 2 will use it" scaffolding.
82
- - **Every task stays in this repo.** Never add or keep a task that edits, commits or pushes another repo. If the user asks for one, leave it out of the plan and advise filing it as a separate item in that repo's backlog.
82
+ - **Every task stays in this repo** unless `assist config get backlog.crossRepo` prints `true`. Never add or keep a task that edits, commits or pushes another repo. If the user asks for one, leave it out of the plan and ask the user to file it as a separate item in that repo's backlog.
83
83
  - If the user proposes a horizontal split, point out that the earlier phase won't verify (knip will flag the unused exports) and suggest a vertical restructure instead.
84
84
 
85
85
  **To associate an external tracker** (Jira or GitHub — mutually exclusive, one per item; associating one clears the other):
@@ -61,6 +61,8 @@ assist screenshot
61
61
  assist seq auth list
62
62
  assist seq query
63
63
  assist sessions nodes
64
+ assist sessions nodes doctor
65
+ assist sessions nodes logs
64
66
  assist sql auth list
65
67
  assist sql columns
66
68
  assist sql query