| name | ouroboros-config |
| description | Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback) |
/ouroboros:ouroboros-config
Settings for ~/.ouroboros/config.yaml: per-stage runtime/model selects,
global runtime + LLM backend, install badges for missing CLIs, and
env-override warnings.
Usage
ooo config
/ouroboros:ouroboros-config
Trigger keywords: "ooo config", "open settings", "configure ouroboros", "change model", "change agent"
Instructions
Pick the branch that matches where you (the agent) are running. The decisive
question: can the user open a browser pointed at this machine?
Branch A — local harness (Claude Code / Codex on the user's own machine)
-
Launch in the background (the command serves until stopped):
if command -v ouroboros >/dev/null 2>&1; then
ouroboros config
else
uvx --python '>=3.12' --from 'ouroboros-ai[tui]' ouroboros config
fi
The command detects the non-interactive context itself and serves the
settings app over a local web server, auto-opening the user's browser. The
uvx fallback is required for a Marketplace-plugin-only install, where the
MCP server exists but ouroboros is not on PATH. In a development
checkout use uv run ouroboros config.
-
Relay the http://localhost:<port> line from the output so the user can
open it manually if the browser did not pop up.
-
Tell the user: edit → Save → then ask you to stop the server. Remind them
a running MCP server may need a reconnect to pick up backend changes. Tell
them they can reopen these settings any time with ; saving a
model choice never locks it permanently.
