Name the installed skill and explicit home for subscription moves

This commit is contained in:
dev-driver committed 2026-10-23 14:15:14 +00:00
1 parent d0f3943f06
commit 1d4c9d6f93
2 files changed
+9 -7

No files matched your search

@@ -3,7 +3,7 @@
**When this applies:** the person has enabled subscription management for you. Installing this bundle
alone does not enable it. You are the one managing agent, not a second manager competing with the operator.
Read `rig context get skills/core/openrig-user`, "Manage subscriptions across a fleet", for the complete
Read `rig context get skills/openrig-user`, "Manage subscriptions across a fleet", for the complete
move procedure and account-policy conversation. Use `rig <command> --help` for this installed version.
The first supported move is a whole Codex home on Linux, including its peers; not a subset of seats on
one home, Claude moves, or Mac restarts. If a route is missing, report it instead of improvising.
@@ -18,9 +18,11 @@ one home, Claude moves, or Mac restarts. If a route is missing, report it instea
3. Balance machines across subscriptions rather than chasing the latest reset. Read
`rig seat restart <seat> --keep-conversation --plan` for the home and every peer. Skip busy or
service-bearing seats with a reason. Moving the home affects all peers, even those not restarted.
4. On that machine, confirm the selected home with `rig auth status --runtime codex`, then run
`rig auth switch <profile> --runtime codex` with that exact CODEX_HOME. Restart chosen seats with
`rig seat restart <seat> --keep-conversation --reason "<why>"`. Preserve their conversation and settings.
4. Confirm the selected home with `rig auth status --runtime codex --codex-home <home>`, then run
`rig auth switch <profile> --runtime codex --codex-home <home>`. For another machine, add
`--host <id>` to both auth commands and to every `rig seat restart` command in this practice.
Restart chosen seats with `rig seat restart <seat> --keep-conversation --reason "<why>"`.
Preserve their conversation and settings.
5. After a real tool-using turn, run `rig seat restart <seat> --keep-conversation --verify
--expect-account <target Account line>`. Only a matched account **and** an observed error-free tool
turn confirm uptake. Missing evidence is unconfirmed or unknown; a slow reply never warrants a
+3 -3
View File
@@ -73,11 +73,11 @@ const VERIFIED = {
"rig capture": [],
"rig send": [],
"rig provider status": ["--json", "--refresh", "--all-hosts", "--hosts", "--provider"],
"rig auth status": ["--runtime"],
"rig auth switch": ["--runtime"],
"rig auth status": ["--runtime", "--codex-home", "--host"],
"rig auth switch": ["--runtime", "--codex-home", "--host"],
"rig provider moves report": ["--file", "--to", "--follows"],
"rig provider moves": ["--seat", "--limit"],
"rig seat restart": ["--keep-conversation", "--reason", "--plan", "--json", "--verify", "--expect-account"],
"rig seat restart": ["--keep-conversation", "--reason", "--plan", "--json", "--verify", "--expect-account", "--host"],
"rig seat launch": [],
"rig seat handover": ["--dry-run", "--reason", "--source", "--json"],
"rig up": ["--existing", "--plan", "--json"],