@staff0rd/assist 0.243.1 → 0.244.1
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 +8 -0
- package/claude/settings.json +2 -1
- package/dist/commands/sessions/web/bundle.js +54 -54
- package/dist/index.js +3553 -3057
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -243,6 +243,14 @@ The first backlog command in a repository that still has a local `.assist/backlo
|
|
|
243
243
|
- `assist sessions` - Start the web dashboard (same as `sessions web`)
|
|
244
244
|
- `assist sessions web [-p, --port <number>]` - Start the web dashboard with Sessions and Backlog tabs, xterm.js terminals (default port 3100)
|
|
245
245
|
- `assist sessions summarise [-f, --force] [-n, --limit <count>]` - Generate one-line summaries for unsummarised Claude sessions (force re-generates all; limit caps how many to process)
|
|
246
|
+
- `assist daemon run` - Run the sessions daemon in the foreground (normally auto-spawned detached by `assist sessions`)
|
|
247
|
+
- `assist daemon status` - Show sessions daemon status and live sessions
|
|
248
|
+
- `assist daemon stop` - Stop the sessions daemon; running claude sessions resume on next start
|
|
249
|
+
- `assist daemon restart` - Restart the sessions daemon, resuming previously running claude sessions
|
|
250
|
+
|
|
251
|
+
Web sessions are owned by a long-lived daemon process, not the web server: the server is a thin client that relays WebSocket traffic to the daemon over a local IPC socket (unix domain socket at `~/.assist/daemon/daemon.sock`; named pipe `\\.\pipe\assist-sessions-daemon` on Windows). Restarting the web server leaves sessions running with scrollback intact. The daemon logs to `~/.assist/daemon/daemon.log` and auto-exits once no sessions remain and no client has been connected for 60 seconds (it is respawned on demand by the web server).
|
|
252
|
+
|
|
253
|
+
When iterating on assist itself: web server changes only need the `assist sessions` process restarted — sessions survive. Daemon/session-core changes need `assist daemon restart` to load the new code; this kills the PTYs, then claude sessions — including assist sessions that wrap claude, like `assist draft` — are auto-respawned via `claude --resume` with scrollback starting fresh, while run sessions (and assist sessions whose claude sessionId was never discovered) reappear as not-restored tiles that can be retried.
|
|
246
254
|
- `assist next [id]` - Alias for `backlog next [id]`
|
|
247
255
|
- `assist draft` (alias: `feat`) - Launch Claude in `/draft` mode, chain into next on `/next` signal
|
|
248
256
|
- `assist bug` - Launch Claude in `/bug` mode, chain into next on `/next` signal
|
package/claude/settings.json
CHANGED
|
@@ -80,7 +80,8 @@
|
|
|
80
80
|
"SlashCommand(/handover)",
|
|
81
81
|
"Skill(recall)",
|
|
82
82
|
"SlashCommand(/recall)",
|
|
83
|
-
"WebFetch(domain:staffordwilliams.com)"
|
|
83
|
+
"WebFetch(domain:staffordwilliams.com)",
|
|
84
|
+
"Bash(assist daemon status)"
|
|
84
85
|
],
|
|
85
86
|
"deny": [
|
|
86
87
|
"Bash(git commit:*)", "Bash(npm run:*)", "Bash(npx assist:*)"
|