Plan and verify OpenRig startup, shutdown, and recovery. Compare reported status with actual running sessions, distinguish recovery outcomes, and define reboot tests that expose partial failures instead of hiding them behind a fresh launch.
中文简介正在准备中。当前显示英语简介。
Use when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or trusting `rig ps` / lifecycle projections after recovery, or designing proof for a lifecycle scenario. Covers the 4 failure modes (auto-restore creates partial rig; projections report healthier than reality; provider auth treated as impl work; resume succeeds for one runtime fails another) plus the restore-honesty rule (failed resume is FAILED loudly — no auto fresh fallback).
安装前可以查看交给 AI 代理的指令内容。
The family of operations that create, start, stop, resume, restore, snapshot, release, unclaim, and destroy OpenRig-managed topologies. Includes the user story after reboot: "bring my work back without turning a clean recovery into a cleanup project."
If lifecycle is brittle, every higher-level primitive inherits that brittleness. Queue, workflow, seat continuity, cross-host operation, and RSI all assume that rigs and seats can be restored into known states.
rig up / down / restore / resume / snapshot / release / unclaim / destroyrig ps after a reboot or recovery and deciding what to trustresumed / rebuilt / fresh / failed / attention_required)openrig-user skill for CLI surfaceopenrig-operatoropenrig-architectrig ps or lifecycle projections report a healthier state than the runtime actually has. Projections are summaries; the runtime is truth. Don't trust projections silently.Failed resume is FAILED loudly. No automatic fresh fallback. Fresh
launch is explicit follow-up only. This is enforced architecturally
at the daemon level (per architecture.md §7 rule 15).
The locked restore-outcome vocabulary:
| Outcome | Meaning |
|---|---|
resumed | Native runtime resumed the same conversation |
rebuilt | New process assembled from artifacts (session_source: mode: rebuild) |
fresh | New process with no prior continuity |
failed | Restore attempted and failed; no automatic fallback |
attention_required | Recoverable blocker (provider auth refused, etc.); needs operator action |
n-a | Not applicable (terminal nodes, etc.) |
Codex auth-refusal returns attention_required (recoverable); Claude
looksLikeClaudeLoginPrompt returns failed/login_required (terminal).
Cross-runtime alignment is an open follow-up question.
Lifecycle proof should include real reboot or VM-reboot evidence, not only daemon-unit evidence. The minimum useful matrix covers:
| Scenario | What it proves |
|---|---|
| Clean start | Boot from spec into known state |
| Warm resume | rig down → rig up <name> resumes seats |
| Host reboot / tmux socket absence | Recovery from lost tmux connection |
| Provider auth loss | Codex/Claude auth refusal handled honestly |
| Partial boot / partial failure | Some seats up, some failed; honest reporting |
| Intentional operator recovery | Operator-initiated restore from snapshot |
Tier 1: in-process bedrock (daemon-unit evidence). Tier 2: real reboot or disposable Tart VM. Tier 1 alone is not lifecycle proof; it's bedrock.
Treat default policy as part of the primitive, not an afterthought. Lifecycle defaults that are too optimistic for the reliability level actually proven create silent harm:
auto-restore defaults that mask failure modesThe rail sequences restore truth into four rungs:
fully_restored is a Rung 3 execution rollupNaming discipline matters. "Fully restored" and "fully back" are different claims; don't conflate.
openrig-user skill — CLI surface for rig up / down / restore / etc.openrig-operator skill — operator-level discipline for OpenRig itselfseat-continuity-and-handover skill — sub-primitive: occupant-creation modes for restore (resume / rebuild / fresh / failed)session-source-fork skill — forked continuity outcome for fork-based restorepermission-and-capability-preflight skill — provider-auth blocker → escalation pathopenrig/docs/as-built/architecture/lifecycle-snapshot-restore.md (product reference doc) — daemon enforcement of restore-honesty rule还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.
中文简介正在准备中。当前显示英语简介。
Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.
中文简介正在准备中。当前显示英语简介。
Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.
中文简介正在准备中。当前显示英语简介。
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
中文简介正在准备中。当前显示英语简介。
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
中文简介正在准备中。当前显示英语简介。
Configure selected OpenRig command permissions in Claude Code or Codex at the agreed project or user scope. Preserve existing restrictions, verify that settings load and behave as intended, and record additions so they can be removed later.
中文简介正在准备中。当前显示英语简介。