Check whether an Ouroboros update is available and upgrade after the user chooses to proceed. The native updater preserves the installation manager, environment, and optional dependencies, then provides restart guidance for the host integrations.
Check for updates and upgrade Ouroboros to the latest version
Review the instructions the agent will receive before you install.
Upgrade Ouroboros without changing the installation's manager, environment, or optional-dependency profile.
ooo update
/ouroboros:update
The native command is the single source of truth. Run it with the active runtime's run_shell capability.
Run ouroboros update --check.
ask_user capability) to choose Update now or Skip. On Update now, run ouroboros update --yes. When the user actively uses both Claude Code and Codex, run ouroboros update --yes --runtime all instead; it refreshes both host integrations without changing the configured execution backend. Show the command's result.If the check fails but ouroboros update --help works, report the native error and stop. Never substitute a manual upgrade, and never infer ownership from 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 install that predates the receipt-bound updater. Fail closed: only a read-only ouroboros --version is allowed. Explain that the original manager, environment, and extras cannot be proven, and ask the user to rerun their exact original install command (including its ouroboros-ai[...] extras and custom manager root), or to do a fresh isolated install if they do not know it. Run no package upgrade, plugin refresh, or setup command on this path.
After a successful update, relay the command's restart guidance (Claude may use /reload-plugins or restart; active Codex sessions need a restart). If project instruction content needs regeneration, suggest ooo setup; never edit project instruction files as part of the update.
The updater replays the environment's install receipt, so the Claude SDK and MCP 2 profiles are never combined or substituted. Other options: --dry-run, --prerelease; see ouroboros update --help.
End the final response with exactly one line ◆ <current state> → next: <recommended action>. Derive the state from live session state via ouroboros_session_status when available, otherwise from this skill's actual outcome. Never use a linear Step N of M footer; when the next step is a real choice, list 2-3 options.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn a multi-file development task or technology migration into a specification with acceptance criteria, then launch background implementation and verification. The workflow clarifies missing requirements, reviews the specification, and tracks progress and blockers through linked jobs.
Register and search existing Git repositories and worktrees, then choose which projects Ouroboros interviews use as context. You can also generate a configuration containing verified build, test, and other check commands for the evaluation workflow.
Stop stuck Ouroboros executions or background jobs by ID, or cancel all running and paused executions in the current project. It reports whether cancellation is complete or has been requested, with guidance for checking the final status.
Verify finished work against acceptance criteria using executable checks and a review of whether each requirement is met. Multiple models can review uncertain cases, and rejected work can enter an automated repair loop when the required Seed is available.
Start and monitor an Ouroboros development loop that revises project concepts and acceptance criteria, the conditions for judging completion. Run and evaluate successive generations, focus revisions on failed criteria, inspect progress, or rewind to an earlier generation.
Turn a vague development idea into clear goals, constraints, and acceptance criteria through a guided interview. It checks unresolved decisions and confirms the agreed goal before moving toward a Seed, the requirements document used by Ouroboros.