Skip to main content
command CX Codex

uninstall — Claude Code command: what it does, how to install

uninstall removes flow-next from your repository. It cleans docs markers and generates safe terminal commands for deleting project files.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What uninstall does

This command runs an interactive removal process for flow-next. It triggers AskUserQuestion to confirm whether you want to proceed and lets you choose between keeping .flow/ specs or wiping everything completely.

Doc cleanup happens automatically. The agent removes <!-- BEGIN FLOW-NEXT --> blocks and model-routing scaffolds from CLAUDE.md and AGENTS.md. If routing tags appear corrupted or mismatched, the command leaves files untouched and flags the problem. It also strips setup stamps from .flow/meta.json.

Destructive file operations are not executed directly by the assistant. Instead, the prompt outputs exact bash snippets for you to run, such as removing .flow or deleting auto-generated agents in .codex/agents/. You need to run those cleanup commands in your shell manually.

What it helps with

  • strip flow-next markers from CLAUDE.md and AGENTS.md
  • prepare commands to purge or preserve .flow task directories
  • remove generated agent configs from .codex/agents/ safely
  • clean up model routing scaffold blocks without breaking custom docs

Example prompts for the agent

  • /uninstall
  • Remove flow-next from this project but keep my tasks
  • Uninstall flow-next and clean up CLAUDE.md

How to install uninstall

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

2Manually: put the files in place

.claude/commands/uninstall.md

Call it with /uninstall. For all projects use ~/.claude/commands/

Questions about uninstall

How to install uninstall in Claude Code?

Add the repository and install the plugin by running /plugin marketplace add gmickel/flow-next followed by /plugin install flow-next@flow-next.

What does the uninstall command do?

It asks whether to keep your task specs, removes configuration markers from documentation files, and provides bash commands for final folder cleanup.

Why does uninstall require manual command execution?

Destructive operations like rm -rf require human confirmation. In addition, safeguards like Destructive Command Guard actively block AI agents from deleting directories directly.

Source text

uninstall.md · MIT
---
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:
```bash
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.
```

© Gordon Mickel · MIT · gmickel/flow-next

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set70

The whole set →
flow-next-make-pr flow-next-make-pr is a Claude Code skill that builds a briefing from an aid artifact and opens or updates a PR through gh. It detects the spec from the branch and accepts options for draft state, base branch, and dry runs. CX Codex +1 ★ 730repo stars flow-next-worktree-kit flow-next-worktree-kit is a Claude Code skill that creates, switches, and removes git worktrees and copies .env files between them. It supports parallel feature work without switching branches. CX Codex +1 ★ 730repo stars flow-next-land The flow-next-land skill handles feedback and CI checks for a named pull request, then squash-merges it when authorized and ready. Use it when asked to land a specific PR. CX Codex +1 ★ 730repo stars flow-next-make-pr flow-next-make-pr opens a pull request through gh, with the briefing body rendered by flowctl from the flow-next spec state. Fits repos where PRs are expected to follow a spec. CX Codex +1 ★ 730repo stars refine refine is a Claude Code command that asks one focused round of questions about a spec, task, or file, or researches related documentation. CX Codex +1 ★ 730repo stars workflow-scout workflow-scout scans repository CI/CD configs, PR and issue templates, automated review bots, and release tooling for readiness checks. CX Codex ★ 730repo stars tooling-scout tooling-scout scans projects for linters, formatters, type checkers and hooks. It is invoked by /flow-next:prime and should not be called directly. CX Codex ★ 730repo stars flow-next-resolve-pr flow-next-resolve-pr coordinates resolution of GitHub PR review feedback, dispatches resolver agents across threads, and closes discussions via GraphQL. CX Codex +1 ★ 730repo stars

Project sponsors

Companies that keep this analytics open