一键导入
config
Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)
菜单
Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)
| name | config |
| description | Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback) |
Settings for ~/.ouroboros/config.yaml: per-stage runtime/model selects,
global runtime + LLM backend, install badges for missing CLIs, and
env-override warnings.
ooo config
/ouroboros:config
Trigger keywords: "ooo config", "open settings", "configure ouroboros", "change model", "change agent"
Pick the branch that matches where you (the agent) are running. The decisive question: can the user open a browser pointed at this machine?
Launch in the background (the command serves until stopped):
ouroboros config
The command detects the non-interactive context itself and serves the
settings app over a local web server, auto-opening the user's browser.
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.
The user cannot see a browser opened here, but may be able to reach this host. Serve without auto-open and hand over the URL:
ouroboros config --web --host 0.0.0.0 --no-browser
Relay the printed URL with this host's address substituted, plus the SSH
tunnel fallback the command prints
(ssh -L <port>:localhost:<port> <this-host>).
Do NOT start a server nobody can reach. Drive the same settings conversationally over the scriptable surface:
Show the current state:
ouroboros config show
Present the user a short menu in chat — default agent, per-stage agents, per-stage models — with the current values, and ask what to change.
Apply each choice with the validated setter (same write path as the GUI):
ouroboros config set orchestrator.runtime_backend <agent>
ouroboros config set orchestrator.runtime_profile.stages.<interview|execute|evaluate|reflect> <agent>
ouroboros config set clarification.default_model <model> # interview & seed
ouroboros config set evaluation.semantic_model <model> # evaluate
ouroboros config set resilience.reflect_model <model> # reflect
ouroboros config set llm.backend <backend> # internal LLM calls
Confirm with ouroboros config show and summarize what changed.
If a set is rejected, relay the validation error verbatim — it lists the
valid keys/values.
If the command fails with a missing-dependency hint, relay it verbatim
(pip install 'ouroboros-ai[tui]'). Scriptable edits always remain on
ouroboros config show|set|backend|init|validate.
End your final message with the state breadcrumb footer (RFC #1392), e.g.:
◆ Settings GUI serving at <url> → next: Save in browser, then stop the server
◆ Config updated via chat (<keys>) → next: reconnect MCP if the backend changed
Guided onboarding wizard for Ouroboros setup
Execute a Seed specification through the workflow engine
Generate validated Seed specifications from interview results
Full reference guide for Ouroboros commands and agents
First-touch experience for new Ouroboros users
Socratic interview to crystallize vague requirements