/uninstall

name: uninstall
description: Remove flow-next files from project
disable-model-invocation: true

Flow-Next Uninstall

Use `AskUserQuestion` to confirm:

**Question 1:** "Remove flow-next from this project?"

• "Yes, uninstall"
• "Cancel"

If cancel → stop.

**Question 2:** "Keep your .flow/ tasks and specs?"

• "Yes, keep tasks" → partial uninstall
• "No, remove everything" → full uninstall

Generate removal instructions

Based on answers, generate the appropriate commands and print them for the user to run manually.

**If keeping tasks:**

Setup copies nothing into `.flow/`, so uninstall there is marker removal: strip the `<!-- BEGIN FLOW-NEXT -->`...`<!-- END FLOW-NEXT -->` block from CLAUDE.md / AGENTS.md (the "Clean up docs" section below does that) and remove the `setup_version` / `setup_mode` stamps from `.flow/meta.json`.

**Legacy cleanup — only when those paths actually exist** (repos set up before copy-less installs). Print this for the user to run manually; omit it entirely when none exist:

To complete uninstall, run these commands manually:

rm -rf .flow/bin .flow/templates .flow/usage.md

**If removing everything:**

To complete uninstall, run these commands manually:

rm -rf .flow

**Always check for Codex agent configs and add if any exist.** On Codex, setup copies flow-next's agent configs into `.codex/agents/`; each starts with `# Auto-generated by sync-codex.sh`. Remove only those, so user-authored agents stay:

if grep -lq '^# Auto-generated by sync-codex.sh' .codex/agents/*.toml 2>/dev/null; then
  echo "grep -l '^# Auto-generated by sync-codex.sh' .codex/agents/*.toml | xargs rm -f"
fi

Clean up docs (AI can do this)

For CLAUDE.md and AGENTS.md: if file exists, remove everything between `<!-- BEGIN FLOW-NEXT -->` and `<!-- END FLOW-NEXT -->` (inclusive). This is safe for the AI to execute.

**Also remove the optional model-routing scaffold block** (written by `/flow-next:setup`) from the same files. It is a *second*, independent marker pair: `<!-- flow-next:model-routing:start -->` … `<!-- flow-next:model-routing:end -->`. Apply the deterministic damaged-marker algorithm — line-based, never parsing the fenced content (the block is an example whose routing lines are all HTML comments):

• Count the `<!-- flow-next:model-routing:start -->` and `<!-- flow-next:model-routing:end -->` lines. If there is **exactly one** start marker **and exactly one** end marker **and** the start line precedes the end line → remove the block inclusive (both markers and everything between them).
• **Any other state** — zero or multiple starts, zero or multiple ends, or end-before-start (out of order) → report the block as damaged and **leave the file untouched**. Never guess which markers pair; a hand-edited file is the user's to fix.

Report

Flow-next uninstall prepared.

Cleaned up:
- Flow-next sections from docs (if existed)
- Model-routing scaffold block from docs (if a well-formed marker pair existed; damaged marker states are reported and left untouched)

Run these commands manually to complete removal:
<commands from above>

Why manual? Destructive commands like rm -rf should have human hands on the keyboard.
If you use DCG (Destructive Command Guard), it will block these commands from AI agents - this is intentional protection.