/ouroboros:update
Check for updates and upgrade Ouroboros without changing the installation's
manager, environment, or optional-dependency profile.
Usage
ooo update
/ouroboros:update
Trigger keywords: "ooo update", "update ouroboros", "upgrade ouroboros"
Instructions
When the user invokes this skill:
Use the native command as the single source of truth:
ouroboros update --check
If it reports up to date, report that result and stop.
If it reports an update available, ask the user to choose Update
now or Skip.
If the user chooses Update now, run:
ouroboros update --yes
When the user actively uses both Claude Code and Codex, refresh both host
integrations without changing the configured execution backend:
ouroboros update --yes --runtime all
Show the command's result. The native updater binds the package upgrade and
post-update setup to one receipt-backed installation identity: manager,
environment, recorded profile, and environment-local console script.
If the check exits unsuccessfully but ouroboros update --help works,
report the native error and stop. Do not replace it with a manual
updater. In particular, do not infer ownership from global uv tool list,
pipx list, PATH order, directory names, or the active agent runtime.
If ouroboros update --help does not work, this is a legacy installation
that predates the receipt-bound updater. Fail closed:
- A read-only
ouroboros --version check is allowed.
- Explain that the old skill cannot prove the original manager,
environment, and extras/profile, so it will not mutate the installation.
- Ask the user to rerun the exact original install command (including its
ouroboros-ai[...] extras and custom manager root) to reach a version
with the native updater.
- If the user does not know that identity, recommend a fresh isolated
install rather than guessing.
- Do not run package upgrades, plugin refreshes, or setup commands from this
legacy path.
After a successful update, relay the runtime-specific restart guidance from
the native command. If project instruction content also needs regeneration,
suggest ooo setup; do not edit project instruction files as part of the
package update.
Safety contract
- PyPI is the version source of truth; fully yanked releases are excluded.
uv and pipx upgrades replay the running environment's local receipt,
preserving base, [tui], [mcp,tui], [claude,tui], [all], and
other recorded profiles.
- The Claude SDK and MCP 2 profiles are never combined or substituted.
- Missing or ambiguous installation identity is a non-mutating error.
- Automatic runtime refresh preserves the configured backend and the existing
OpenCode
plugin/subprocess topology instead of inferring a replacement
from PATH.
- Runtime executable identity follows the supported environment override,
then the persisted
orchestrator.*_cli_path, then PATH. The chosen exact
executable is validated and reused for plugin/setup refresh so a stale PATH
binary cannot replace an operator-selected runtime.
--runtime all refreshes the Claude and Codex plugin integrations plus
installed runtime artifacts without changing the configured execution
backend. Active Codex sessions still need a restart because Codex does not
currently retain an in-use plugin generation; Claude may use
/reload-plugins or restart.
ouroboros update supports --check, --yes, --dry-run,
--prerelease, and --runtime; see ouroboros update --help.
RFC #1392 State Breadcrumb Footer
Your final response MUST end with exactly one breadcrumb footer line:
◆ <current state> → next: <recommended action>
Derive <current state> from live session state via ouroboros_session_status
when that MCP projection is available; otherwise
derive it from this skill's actual outcome. Never use a linear Step N of M footer
because Ouroboros is an evolutionary loop. When the next action is
genuinely a choice, list 2-3 honest options in the next: clause. The
breadcrumb line must be the last line of the response.
1---
2name: update
3description: "Check for updates and upgrade Ouroboros to the latest version"
4metadata:
5 source: https://skillmd.com/skills/q00/update
6---
7
8# /ouroboros:update
9
10Check for updates and upgrade Ouroboros without changing the installation's
11manager, environment, or optional-dependency profile.
12
13## Usage
14
15```
16ooo update
17/ouroboros:update
18```
19
20**Trigger keywords:** "ooo update", "update ouroboros", "upgrade ouroboros"
21
22## Instructions
23
24When the user invokes this skill:
25
261. Use the native command as the single source of truth:
27
28 ```bash
29 ouroboros update --check
30 ```
31
32 - If it reports **up to date**, report that result and stop.
33 - If it reports an **update available**, ask the user to choose **Update
34 now** or **Skip**.
35 - If the user chooses **Update now**, run:
36
37 ```bash
38 ouroboros update --yes
39 ```
40
41 When the user actively uses both Claude Code and Codex, refresh both host
42 integrations without changing the configured execution backend:
43
44 ```bash
45 ouroboros update --yes --runtime all
46 ```
47
48 Show the command's result. The native updater binds the package upgrade and
49 post-update setup to one receipt-backed installation identity: manager,
50 environment, recorded profile, and environment-local console script.
51
522. If the check exits unsuccessfully but `ouroboros update --help` works,
53 report the native error and stop. **Do not** replace it with a manual
54 updater. In particular, do not infer ownership from global `uv tool list`,
55 `pipx list`, PATH order, directory names, or the active agent runtime.
56
573. If `ouroboros update --help` does not work, this is a legacy installation
58 that predates the receipt-bound updater. Fail closed:
59
60 - A read-only `ouroboros --version` check is allowed.
61 - Explain that the old skill cannot prove the original manager,
62 environment, and extras/profile, so it will not mutate the installation.
63 - Ask the user to rerun the exact original install command (including its
64 `ouroboros-ai[...]` extras and custom manager root) to reach a version
65 with the native updater.
66 - If the user does not know that identity, recommend a fresh isolated
67 install rather than guessing.
68 - Do not run package upgrades, plugin refreshes, or setup commands from this
69 legacy path.
70
714. After a successful update, relay the runtime-specific restart guidance from
72 the native command. If project instruction content also needs regeneration,
73 suggest `ooo setup`; do not edit project instruction files as part of the
74 package update.
75
76## Safety contract
77
78- PyPI is the version source of truth; fully yanked releases are excluded.
79- `uv` and `pipx` upgrades replay the running environment's local receipt,
80 preserving base, `[tui]`, `[mcp,tui]`, `[claude,tui]`, `[all]`, and
81 other recorded profiles.
82- The Claude SDK and MCP 2 profiles are never combined or substituted.
83- Missing or ambiguous installation identity is a non-mutating error.
84- Automatic runtime refresh preserves the configured backend and the existing
85 OpenCode `plugin`/`subprocess` topology instead of inferring a replacement
86 from PATH.
87- Runtime executable identity follows the supported environment override,
88 then the persisted `orchestrator.*_cli_path`, then PATH. The chosen exact
89 executable is validated and reused for plugin/setup refresh so a stale PATH
90 binary cannot replace an operator-selected runtime.
91- `--runtime all` refreshes the Claude and Codex plugin integrations plus
92 installed runtime artifacts without changing the configured execution
93 backend. Active Codex sessions still need a restart because Codex does not
94 currently retain an in-use plugin generation; Claude may use
95 `/reload-plugins` or restart.
96- `ouroboros update` supports `--check`, `--yes`, `--dry-run`,
97 `--prerelease`, and `--runtime`; see `ouroboros update --help`.
98
99## RFC #1392 State Breadcrumb Footer
100
101Your final response MUST end with exactly one breadcrumb footer line:
102
103```
104◆ <current state> → next: <recommended action>
105```
106
107Derive `<current state>` from live session state via `ouroboros_session_status`
108when that MCP projection is available; otherwise
109derive it from this skill's actual outcome. Never use a linear `Step N of M` footer
110because Ouroboros is an evolutionary loop. When the next action is
111genuinely a choice, list 2-3 honest options in the `next:` clause. The
112breadcrumb line must be the last line of the response.