mirror of
https://github.com/mvschwarz/openrig.git
synced 2026-11-07 05:56:21 -10:00
docs: correct the seat history and task view usage in the 0.7.4 notes
rig seat history takes --rig and --node-id, and checks one reference with --snapshot-id and --history-session-id together; there is no rig terminal preview command (open calls the daemon's preview). The reboot troubleshooting row says a kernel already down stays down. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
dev-driverandClaude Opus 5.5 committed
1 parent
0d1c4b3d3c
commit
6d9e8e271a
4 files changed
+16
-12
No files matched your search
+5
-4
@@ -127,10 +127,11 @@ down. It is built from the commit tagged `v0.7.4`. The changes since 0.7.3:
|
||||
|
||||
**Resuming the conversation you chose**
|
||||
|
||||
- **`rig seat history <seat>`** lists the recorded Claude and Codex
|
||||
- **`rig seat history --rig <id> --node-id <id>`** lists the recorded Claude and Codex
|
||||
conversations this exact node could resume, read-only and without native
|
||||
tokens (`--json`; `--snapshot-id` or `--history-session-id` checks one
|
||||
reference). ([#2100](https://github.com/mvschwarz/openrig/pull/2100))
|
||||
tokens (`--json`; `--snapshot-id` with `--history-session-id` checks one
|
||||
reference it returned). The rig ID is `rigId` in `rig ps --nodes --json`, and the
|
||||
node ID is `identity.nodeId` in `rig whoami --session <seat> --json`. ([#2100](https://github.com/mvschwarz/openrig/pull/2100))
|
||||
- **A client can resume the history a person reviewed** for an exact node,
|
||||
through the daemon's startup review. Applying it rechecks the choice and the
|
||||
settings through the existing restore path, and refuses, rather than
|
||||
@@ -144,7 +145,7 @@ down. It is built from the commit tagged `v0.7.4`. The changes since 0.7.3:
|
||||
|
||||
**Task views**
|
||||
|
||||
- `rig terminal preview` and `open` accept `qitem:<id>`: the current local
|
||||
- `rig terminal open` and the daemon's terminal preview accept `qitem:<id>`: the current local
|
||||
owners of that task, meaning its pending, in-progress and blocked rows
|
||||
through explicitly linked successors, without closed predecessors or past
|
||||
senders. Stopped, missing, external and unresolved owners are named, and
|
||||
|
||||
@@ -841,7 +841,7 @@ the lifecycle API without booting a new kernel, then stop the remaining rigs.
|
||||
| Shared terminal is absent | Inspect the existing kernel binding and recovery state; use standalone `rig tui` while resolving it. |
|
||||
| Viewing terminal was closed | Open the conversations again with `rig terminal open saved:kernel --window`; `rig tui --shared` is only the dashboard fallback if that window cannot open. Do not relaunch the team. |
|
||||
| Daemon restarted but tmux survived | Re-read `rig status` and the existing queue; a daemon restart is not a fresh project. |
|
||||
| Host reboot lost tmux sessions | Starting the daemon restores the kernel by itself when all of its seats were lost; check `rig status`, and if it reports the restore failed, run `rig up kernel --existing`. For other rigs, open `rig`, start the daemon if needed (press **S** if it opens on the work views), and select the existing rig and seats. Resume is the default; a fresh conversation needs a separate decision. |
|
||||
| Host reboot lost tmux sessions | Starting the daemon restores the kernel by itself when that start finds all of its seats lost; a kernel that was already down before the reboot stays down, and `rig start` names `rig up kernel --existing`. Check `rig status`, and if it reports the restore failed, run `rig up kernel --existing`. For other rigs, open `rig`, start the daemon if needed (press **S** if it opens on the work views), and select the existing rig and seats. Resume is the default; a fresh conversation needs a separate decision. |
|
||||
| Launch reports no usable snapshot | Inspect the existing rig and retained project files, then follow the same-seat recovery below. |
|
||||
| Work is waiting on a prompt or decision | Read the row, transition and named prompt; preserve the obligation until the missing decision arrives. |
|
||||
|
||||
|
||||
@@ -47,10 +47,12 @@ after an upgrade it can still hold the previous version's note.
|
||||
- **Serve newer MCP clients:** clients on protocol revision 2026-07-28 (no `initialize`, the version on every request,
|
||||
possibly opening with `server/discover`) work with `rig mcp serve` over stdio or `--http`, beside clients on the 2025
|
||||
revisions, on the same endpoint.
|
||||
- **List the conversations a seat could resume:** `rig seat history <seat>` (`--json`), read-only and without native
|
||||
tokens; `--snapshot-id <id>` or `--history-session-id <id>` checks one reference it returned. A client can then ask the
|
||||
daemon's startup review for that node to resume the history the person reviewed.
|
||||
- **Preview or open a task's current owners:** `rig terminal preview qitem:<id>` and `rig terminal open qitem:<id>`.
|
||||
- **List the conversations a seat could resume:** `rig seat history --rig <id> --node-id <id>` (`--json`), read-only and
|
||||
without native tokens; `--snapshot-id <id>` with `--history-session-id <id>` checks one reference it returned. The IDs
|
||||
are `rigId` in `rig ps --nodes --json` and `identity.nodeId` in `rig whoami --session <seat> --json`. A client can then
|
||||
ask the daemon's startup review for that node to resume the history the person reviewed.
|
||||
- **Preview or open a task's current owners:** `rig terminal open qitem:<id>`; the daemon's preview,
|
||||
`GET /api/terminal/preview?view=qitem:<id>`, returns the same view without opening it.
|
||||
|
||||
## Behaviour that changed
|
||||
|
||||
|
||||
@@ -603,9 +603,10 @@ because someone lost work once.
|
||||
When your user says OpenRig isn't working, start with **`rig context get help`**: the one help guide for the installed
|
||||
version, from checking the environment to a useful report to the OpenRig team.
|
||||
|
||||
- **`rig seat history <seat>`** — which recorded Claude or Codex conversations this exact node
|
||||
could resume, read-only (`--json`; check one reference with `--snapshot-id` or
|
||||
`--history-session-id`). A client can then ask the daemon's startup review for that node to resume
|
||||
- **`rig seat history --rig <id> --node-id <id>`** — which recorded Claude or Codex conversations this exact node
|
||||
could resume, read-only (`--json`; check one reference with `--snapshot-id` and `--history-session-id` together).
|
||||
The IDs are `rigId` in `rig ps --nodes --json` and `identity.nodeId` in `rig whoami --session <seat> --json`.
|
||||
A client can then ask the daemon's startup review for that node to resume
|
||||
the history the person reviewed; it rechecks the choice and refuses rather than substitute another
|
||||
conversation or start fresh.
|
||||
- **`rig start`** — the box rebooted and everything is gone: bring the whole topology back in one
|
||||
|
||||
Reference in new issue
Block a user