ouroboros-ai 0.26.2.dev37__tar.gz → 0.26.3.dev1__tar.gz

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "ouroboros",
       "description": "Transform vague ideas into validated seed specifications through Socratic questioning and ontological analysis",
-      "version": "0.26.1",
+      "version": "0.26.2",
       "author": {
         "name": "Q00",
         "email": "jqyu.lee@gmail.com"

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ouroboros",
-  "version": "0.26.1",
+  "version": "0.26.2",
   "description": "Self-improving AI workflow system. Crystallize requirements before execution with Socratic interview, ambiguity scoring, and 3-stage evaluation.",
   "author": {
     "name": "Q00",

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ouroboros-ai
-Version: 0.26.2.dev37
+Version: 0.26.3.dev1
 Summary: Specification-first workflow engine for AI coding agents. Works with Claude Code and Codex CLI.
 Author-email: Q00 <jqyu.lee@gmail.com>
 License-File: LICENSE
@@ -143,6 +143,17 @@ See runtime guides: [Claude Code](./docs/runtime-guides/claude-code.md) · [Code
 
 </details>
 
+<details>
+<summary><strong>Uninstall</strong></summary>
+
+```bash
+ouroboros uninstall
+```
+
+Removes all configuration, MCP registration, and data. See [UNINSTALL.md](./UNINSTALL.md) for details.
+
+</details>
+
 > **Python >= 3.12 required.** See [pyproject.toml](./pyproject.toml) for the full dependency list.
 
 ---

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/README.ko.md

@@ -127,6 +127,17 @@ ouroboros setup                         # 런타임 설정
 
 </details>
 
+<details>
+<summary><strong>완전 삭제</strong></summary>
+
+```bash
+ouroboros uninstall
+```
+
+모든 설정, MCP 등록, 데이터를 제거합니다. 자세한 내용은 [UNINSTALL.md](./UNINSTALL.md)를 참고하세요.
+
+</details>
+
 <details>
 <summary><strong>무슨 일이 일어났나요?</strong></summary>
 

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/README.md

@@ -103,6 +103,17 @@ See runtime guides: [Claude Code](./docs/runtime-guides/claude-code.md) · [Code
 
 </details>
 
+<details>
+<summary><strong>Uninstall</strong></summary>
+
+```bash
+ouroboros uninstall
+```
+
+Removes all configuration, MCP registration, and data. See [UNINSTALL.md](./UNINSTALL.md) for details.
+
+</details>
+
 > **Python >= 3.12 required.** See [pyproject.toml](./pyproject.toml) for the full dependency list.
 
 ---

ouroboros_ai-0.26.3.dev1/UNINSTALL.md

@@ -0,0 +1,66 @@
+# Clean Uninstall Guide
+
+## One Command
+
+```bash
+ouroboros uninstall
+```
+
+This interactively removes all Ouroboros configuration:
+- MCP server registration (`~/.claude/mcp.json`, `~/.codex/config.toml`)
+- CLAUDE.md integration block (`<!-- ooo:START -->` ... `<!-- ooo:END -->`)
+- Codex rules and skills (`~/.codex/rules/ouroboros.md`, `~/.codex/skills/ouroboros/`)
+- Project-level config (`.ouroboros/`)
+- Data directory (`~/.ouroboros/` — config, credentials, DB, seeds, logs, locks, prefs)
+
+Then finish with:
+
+```bash
+uv tool uninstall ouroboros-ai            # or: pip uninstall ouroboros-ai
+claude plugin uninstall ouroboros         # if using Claude Code plugin
+```
+
+### Options
+
+| Flag | Effect |
+|:-----|:-------|
+| `-y`, `--yes` | Skip confirmation prompt |
+| `--dry-run` | Preview what would be removed, change nothing |
+| `--keep-data` | Keep entire `~/.ouroboros/` (config, credentials, seeds, DB, logs) |
+
+### Inside Claude Code
+
+Inside an active Claude Code session, type:
+
+```
+/ouroboros:setup --uninstall
+```
+
+This is a **skill command** (not a CLI flag) that removes MCP registration and the CLAUDE.md block interactively.
+
+---
+
+## What Lives Where
+
+| Path | Created by | Contents |
+|:-----|:-----------|:---------|
+| `~/.claude/mcp.json` | `ooo setup` / `ouroboros setup` | MCP server entry |
+| `~/.codex/config.toml` | `ouroboros setup --runtime codex` | Codex MCP section |
+| `~/.codex/rules/ouroboros.md` | `ouroboros setup --runtime codex` | Codex rules |
+| `~/.codex/skills/ouroboros/` | `ouroboros setup --runtime codex` | Codex skills |
+| `CLAUDE.md` | `ooo setup` | Command reference block |
+| `~/.ouroboros/config.yaml` | `ouroboros setup` | Runtime configuration |
+| `~/.ouroboros/credentials.yaml` | `ouroboros setup` | API credentials |
+| `~/.ouroboros/ouroboros.db` | First run | Event store + brownfield registry |
+| `~/.ouroboros/seeds/` | `ooo seed` / `ooo interview` | Generated seed specs |
+| `~/.ouroboros/data/` | `ooo interview` | Interview state |
+| `~/.ouroboros/logs/` | Any run | Log files |
+| `~/.ouroboros/locks/` | `ooo run` | Heartbeat locks |
+| `~/.ouroboros/prefs.json` | `ooo setup` | Preferences |
+| `.ouroboros/` (project) | `ooo evaluate` | Mechanical eval config |
+
+## What Is NOT Removed
+
+- Your project source code and git history
+- Generated seed YAML files copied outside `~/.ouroboros/seeds/`
+- Package manager caches (run `uv cache clean ouroboros-ai` or `pip cache purge` if needed)

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/docs/cli-reference.md

@@ -42,7 +42,8 @@ ouroboros [OPTIONS] COMMAND [ARGS]...
 | `init` | Start interactive interview to refine requirements |
 | `run` | Execute Ouroboros workflows |
 | `cancel` | Cancel stuck or orphaned executions |
-| `config` | Manage Ouroboros configuration |
+| `config` | Manage Ouroboros configuration (show, switch backend, set values) |
+| `uninstall` | Cleanly remove all Ouroboros configuration from your system |
 | `status` | Check Ouroboros system status |
 | `tui` | Interactive TUI monitor for real-time workflow monitoring |
 | `monitor` | Shorthand for `tui monitor` |
@@ -311,11 +312,9 @@ ouroboros cancel execution orch_abc123 --reason "Stuck for 2 hours"
 
 Manage Ouroboros configuration.
 
-> **Current state:** the `config` subcommands are scaffolding. They currently print placeholder output and do not mutate `~/.ouroboros/config.yaml`. Use `ouroboros setup` for initial runtime setup, then edit `~/.ouroboros/config.yaml` directly for manual changes.
-
 ### `config show`
 
-Display current configuration.
+Display current configuration summary, or a specific section.
 
 ```bash
 ouroboros config show [SECTION]
@@ -325,16 +324,43 @@ ouroboros config show [SECTION]
 
 | Argument | Description |
 |----------|-------------|
-| `SECTION` | Configuration section to display (e.g., `providers`) |
+| `SECTION` | Configuration section to display (e.g., `orchestrator`, `llm`, `consensus`) |
 
 **Examples:**
 
 ```bash
-# Show all configuration
+# Show configuration summary (backend, CLI path, DB, log level)
 ouroboros config show
 
-# Show only providers section
-ouroboros config show providers
+# Show only orchestrator section
+ouroboros config show orchestrator
+```
+
+### `config backend`
+
+Show or switch the runtime backend. This sets both `orchestrator.runtime_backend` and `llm.backend` together — they are always kept in sync for simplicity. Advanced users can decouple them with `config set`.
+
+```bash
+ouroboros config backend [BACKEND]
+```
+
+**Arguments:**
+
+| Argument | Description |
+|----------|-------------|
+| `BACKEND` | Backend to switch to: `claude` or `codex`. Omit to show current |
+
+**Examples:**
+
+```bash
+# Show current backend
+ouroboros config backend
+
+# Switch to Codex CLI
+ouroboros config backend codex
+
+# Switch to Claude Code
+ouroboros config backend claude
 ```
 
 ### `config init`
@@ -349,7 +375,7 @@ Creates `~/.ouroboros/config.yaml` and `~/.ouroboros/credentials.yaml` with defa
 
 ### `config set`
 
-Set a configuration value.
+Set a configuration value using dot notation.
 
 ```bash
 ouroboros config set KEY VALUE
@@ -365,13 +391,16 @@ ouroboros config set KEY VALUE
 **Examples:**
 
 ```bash
-# Placeholder command surface (does not yet write files)
-ouroboros config set orchestrator.runtime_backend codex
+# Change log level
+ouroboros config set logging.level debug
+
+# Override LLM backend separately from runtime backend
+ouroboros config set llm.backend litellm
 ```
 
 ### `config validate`
 
-Validate current configuration.
+Validate current configuration. Checks that the runtime backend is supported and the CLI binary path exists.
 
 ```bash
 ouroboros config validate
@@ -379,6 +408,57 @@ ouroboros config validate
 
 ---
 
+## `ouroboros uninstall`
+
+Cleanly remove all Ouroboros configuration from your system. Reverses everything `ouroboros setup` did.
+
+```bash
+ouroboros uninstall [OPTIONS]
+```
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--keep-data` | Keep entire `~/.ouroboros/` directory (config, credentials, seeds, logs, DB) |
+| `--dry-run` | Show what would be removed without actually deleting |
+| `-y, --yes` | Skip confirmation prompt |
+
+**Examples:**
+
+```bash
+# Interactive uninstall (shows what will be removed, asks for confirmation)
+ouroboros uninstall
+
+# Non-interactive
+ouroboros uninstall -y
+
+# Preview only
+ouroboros uninstall --dry-run
+
+# Remove MCP/artifacts but keep ~/.ouroboros/
+ouroboros uninstall --keep-data
+```
+
+**What it removes:**
+
+- `ouroboros` entry from `~/.claude/mcp.json`
+- `[mcp_servers.ouroboros]` section from `~/.codex/config.toml`
+- `~/.codex/rules/ouroboros.md` and `~/.codex/skills/ouroboros/`
+- `<!-- ooo:START -->` … `<!-- ooo:END -->` block from `CLAUDE.md`
+- `.ouroboros/` directory in the current project
+- `~/.ouroboros/` directory (unless `--keep-data`)
+
+**What it does NOT remove:**
+
+- The Python package — run `pip uninstall ouroboros-ai` or `uv tool uninstall ouroboros-ai` separately
+- The Claude Code plugin — run `claude plugin uninstall ouroboros` separately
+- Your project source code or git history
+
+See [UNINSTALL.md](../UNINSTALL.md) for the full guide.
+
+---
+
 ## `ouroboros status`
 
 Check Ouroboros system status.

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/scripts/install.sh

@@ -140,11 +140,9 @@ if [ "$HAS_UV" = true ]; then
 elif [ "$HAS_PIPX" = true ]; then
   INSTALL_METHOD="pipx"
   if [ -n "$PRE_FLAG" ]; then
-    pipx install --pip-args='--pre' "$INSTALL_SPEC" 2>/dev/null \
-      || pipx upgrade --pip-args='--pre' "$INSTALL_SPEC"
+    pipx install --force --pip-args='--pre' "$INSTALL_SPEC"
   else
-    pipx install "$INSTALL_SPEC" 2>/dev/null \
-      || pipx upgrade "$INSTALL_SPEC"
+    pipx install --force "$INSTALL_SPEC"
   fi
 else
   INSTALL_METHOD="pip"
@@ -184,11 +182,11 @@ if command -v claude &>/dev/null; then
 
   # MCP command matches the installer that actually ran in step 3
   if [ "$INSTALL_METHOD" = "uv" ]; then
-    OUROBOROS_ENTRY='{"command":"uvx","args":["--from","ouroboros-ai[claude]","ouroboros","mcp","serve"],"timeout":600}'
+    OUROBOROS_ENTRY='{"command":"uvx","args":["--from","ouroboros-ai[claude]","ouroboros","mcp","serve"]}'
   elif [ "$INSTALL_METHOD" = "pipx" ]; then
-    OUROBOROS_ENTRY='{"command":"ouroboros","args":["mcp","serve"],"timeout":600}'
+    OUROBOROS_ENTRY='{"command":"ouroboros","args":["mcp","serve"]}'
   else
-    OUROBOROS_ENTRY='{"command":"python3","args":["-m","ouroboros","mcp","serve"],"timeout":600}'
+    OUROBOROS_ENTRY='{"command":"python3","args":["-m","ouroboros","mcp","serve"]}'
   fi
 
   # Find a working Python: system python3, or uv-managed python

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/skills/pm/SKILL.md

@@ -15,7 +15,26 @@ PM-focused Socratic interview that produces a Product Requirements Document.
 ToolSearch query: "+ouroboros pm_interview"
 ```
 
-If not found → tell user to run `ooo setup` first. Stop.
+If not found → **diagnose before telling user to run setup**:
+
+1. Check if MCP is already configured:
+   ```bash
+   grep -q '"ouroboros"' ~/.claude/mcp.json 2>/dev/null && echo "CONFIGURED" || echo "NOT_CONFIGURED"
+   ```
+
+2. **If NOT_CONFIGURED** → tell user to run `ooo setup` first. Stop.
+
+3. **If CONFIGURED** → MCP is registered but the server isn't connecting. Do NOT tell the user to run `ooo setup` again. Instead show:
+   ```
+   Ouroboros MCP is configured but not connected.
+
+   Try these steps in order:
+   1. Restart Claude Code (Cmd+Shift+P → "Reload Window" or close/reopen terminal)
+   2. Check MCP status: type /mcp in Claude Code
+   3. If ouroboros shows "error", try: ooo update
+   4. If still failing, re-run: ooo setup
+   ```
+   Stop.
 
 ### Step 2: Start Interview
 

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/skills/setup/SKILL.md

@@ -123,16 +123,44 @@ Runtime backend            [✓] Detected
 
 | Environment | Mode | Action |
 |:------------|:-----|:-------|
-| uvx + uv Python >= 3.12 | **Ready** | Proceed to MCP registration |
-| System Python >= 3.12 | **Ready** | Proceed to MCP registration |
+| uvx + Python >= 3.12 | **Ready** | Proceed to MCP registration (uvx mode — extras always included) |
+| No uvx + `ouroboros` binary in PATH | **Check deps** | Verify `[claude]` extras, then proceed (binary mode) |
+| No uvx + Python >= 3.12 + `python3 -m ouroboros` works | **Check deps** | Verify `[claude]` extras, then proceed (pip mode) |
 | uvx + Python < 3.12 only | **Install needed** | Run `uv python install 3.12` then proceed |
-| No uvx | **Install needed** | Run `curl -LsSf https://astral.sh/uv/install.sh \| sh` then `uv python install 3.12` |
+| No uvx + no ouroboros binary + no pip package | **Install needed** | Install uv first, then proceed |
 
-**IMPORTANT**: If Python >= 3.12 is not available, DO NOT skip to "Plugin-Only mode". Guide the user to install the prerequisites. MCP is required for the full Ouroboros experience.
+**For binary/pip modes — verify `[claude]` extras are installed:**
+
+Check method depends on how ouroboros was installed:
+```bash
+# Detect install method
+pipx list 2>/dev/null | grep -q ouroboros && echo "PIPX" || echo "NOT_PIPX"
+```
+
+- **pipx users** (binary mode, installed via pipx):
+  ```bash
+  pipx runpip ouroboros-ai show claude-agent-sdk 2>/dev/null && echo "DEPS_OK" || echo "DEPS_MISSING"
+  ```
+  If `DEPS_MISSING`: `pipx install --force ouroboros-ai[claude]`
+
+- **pip users** (pip mode):
+  ```bash
+  python3 -c "import claude_agent_sdk" 2>/dev/null && echo "DEPS_OK" || echo "DEPS_MISSING"
+  ```
+  If `DEPS_MISSING`: `python3 -m pip install ouroboros-ai[claude]`
+
+If deps are missing and the user doesn't want to fix manually, recommend uvx:
+```
+Or install uvx (recommended — handles deps automatically):
+  curl -LsSf https://astral.sh/uv/install.sh | sh
+Then re-run: ooo setup
+```
+
+**IMPORTANT**: The MCP server requires one of: (1) uvx, (2) ouroboros binary in PATH, or (3) ouroboros pip-installed. For options 2 and 3, the `[claude]` extra must also be installed. If none are available, guide the user to install uv — do NOT write a non-working fallback to mcp.json.
 
 **If prerequisites are missing, show:**
 ```
-Ouroboros requires Python >= 3.12 for the MCP server.
+Ouroboros requires uvx (recommended) or the ouroboros package installed.
 
 Quick install (< 1 minute):
   curl -LsSf https://astral.sh/uv/install.sh | sh
@@ -173,12 +201,13 @@ This enables:
 
 **Automatically create or update `~/.claude/mcp.json`** (user-level, works across all projects).
 
-Choose the MCP command based on how ouroboros is installed:
-- If `uvx` is available: `{"command": "uvx", "args": ["--from", "ouroboros-ai[claude]", "ouroboros", "mcp", "serve"], "timeout": 600}`
-- If `ouroboros` binary is in PATH (pipx install): `{"command": "ouroboros", "args": ["mcp", "serve"], "timeout": 600}`
-- Fallback (pip install): `{"command": "python3", "args": ["-m", "ouroboros", "mcp", "serve"], "timeout": 600}`
+Choose the MCP command based on how ouroboros is installed (check in order):
+1. If `which uvx` succeeds: `{"command": "uvx", "args": ["--from", "ouroboros-ai[claude]", "ouroboros", "mcp", "serve"]}`
+2. If `which ouroboros` succeeds: `{"command": "ouroboros", "args": ["mcp", "serve"]}`
+3. If `python3 -c "import ouroboros"` succeeds: `{"command": "python3", "args": ["-m", "ouroboros", "mcp", "serve"]}`
+4. If none of the above → **do NOT write to mcp.json**. Instead show the prerequisites message from Step 1 and stop.
 
-If `~/.claude/mcp.json` already exists, merge intelligently (preserve other servers).
+If `~/.claude/mcp.json` already exists, read it, **always overwrite the `ouroboros` key** with the entry above (to fix stale args from older versions), and preserve all other server entries.
 
 **Celebration Checkpoint 2:**
 ```
@@ -217,7 +246,7 @@ A backup will be created: CLAUDE.md.bak
 **If "Preview first", show:**
 ````markdown
 <!-- ooo:START -->
-<!-- ooo:VERSION:0.26.1 -->
+<!-- ooo:VERSION:0.26.2 -->
 # Ouroboros — Specification-First AI Development
 
 > Before telling AI what to build, define what should be built.

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/skills/update/SKILL.md

@@ -80,38 +80,46 @@ When the user invokes this skill:
 
 4. **Run update** (if user chose to update):
 
-   a. **Update PyPI package** — detect the original install method and use the same one:
+   a. **Update PyPI package** — detect the original install method and preserve `[claude]` extras:
 
-   Check which installer was used (in priority order):
+   Check which installer was used:
    ```bash
    uv tool list 2>/dev/null | grep -q ouroboros && echo "uv"
    pipx list 2>/dev/null | grep -q ouroboros && echo "pipx"
    ```
 
+   > This skill runs inside Claude Code, so always use `ouroboros-ai[claude]`
+   > (includes `claude-agent-sdk` and `anthropic` required for MCP tools).
+
    - If installed via **uv tool** (most common with install.sh):
      ```bash
      # For pre-release targets:
-     uv tool install --upgrade --prerelease=allow ouroboros-ai
+     uv tool install --upgrade --prerelease=allow ouroboros-ai[claude]
      # For stable targets:
-     uv tool install --upgrade ouroboros-ai
+     uv tool install --upgrade ouroboros-ai[claude]
      ```
 
    - If installed via **pipx**:
+     > `pipx upgrade` cannot add extras to an existing venv — use `install --force` to reinstall with extras.
      ```bash
      # For pre-release targets:
-     pipx upgrade --pip-args='--pre' ouroboros-ai
+     pipx install --force --pip-args='--pre' ouroboros-ai[claude]
      # For stable targets:
-     pipx upgrade ouroboros-ai
+     pipx install --force ouroboros-ai[claude]
      ```
 
    - If installed via **pip** (fallback):
      ```bash
      # For pre-release targets:
-     python3 -m pip install --upgrade --pre ouroboros-ai
+     python3 -m pip install --upgrade --pre ouroboros-ai[claude]
      # For stable targets:
-     python3 -m pip install --upgrade ouroboros-ai
+     python3 -m pip install --upgrade ouroboros-ai[claude]
      ```
 
+   > **Note**: The `[claude]` extra is critical — it installs `claude-agent-sdk` and
+   > `anthropic` which are required for MCP tool execution. Omitting it causes MCP
+   > tools to fail silently at call time.
+
    b. **Update runtime integration**:
 
    For Claude Code:
@@ -125,7 +133,21 @@ When the user invokes this skill:
    ouroboros setup --runtime codex --non-interactive
    ```
 
-   c. **Verify and update CLAUDE.md version marker**:
+   c. **Refresh MCP server config** (fixes stale args from older versions):
+
+   Run the same setup command used in step b to ensure MCP config is current:
+
+   For Claude Code:
+   ```bash
+   ouroboros setup --runtime claude --non-interactive
+   ```
+
+   For Codex CLI (already handled by step b above — skip this step).
+
+   This ensures `~/.claude/mcp.json` has the latest MCP command and args
+   (e.g., `ouroboros-ai[claude]` extras). Skips if already up to date.
+
+   d. **Verify and update CLAUDE.md version marker**:
    ```bash
    NEW_VERSION=$(ouroboros --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+[a-z0-9.]*')
    echo "Installed: v$NEW_VERSION"

{ouroboros_ai-0.26.2.dev37 → ouroboros_ai-0.26.3.dev1}/src/ouroboros/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.26.2.dev37'
-__version_tuple__ = version_tuple = (0, 26, 2, 'dev37')
+__version__ = version = '0.26.3.dev1'
+__version_tuple__ = version_tuple = (0, 26, 3, 'dev1')
 
 __commit_id__ = commit_id = None