# Ctx Purge

Purge the context-mode knowledge base.

- Repository: https://github.com/mksglu/context-mode (33152 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mksglu/context-mode --skill ctx-purge -g -a claude-code -y`
Codex: `npx skills add mksglu/context-mode --skill ctx-purge -g -a codex -y`
Cursor: `npx skills add mksglu/context-mode --skill ctx-purge -g -a cursor -y`
Gemini CLI: `npx skills add mksglu/context-mode --skill ctx-purge -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add mksglu/context-mode`

## Description

Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Context Mode Purge

Permanently deletes session data for this project. Two scopes are supported (issue #520):

- **Project scope** (`scope: "project"`): wipes EVERYTHING, knowledge base, all session DB rows for every session, events markdown, and stats.
- **Session scope** (`sessionId: "<id>"` or `scope: "session"`): wipes ONLY the matching session's rows + FTS5 chunks. Sibling sessions, project stats, and the FTS5 store file are preserved.

## Instructions

1. **Decide the scope first** with the user:
   - "Wipe just one session?" → ask for the `sessionId`.
   - "Wipe the whole project?" → confirm scope:'project' (this is the destructive, irreversible default).
2. **Warn the user about scope:'project'**. Everything will be deleted:
   - FTS5 knowledge base (all indexed content from `ctx_index`, `ctx_fetch_and_index`, `ctx_batch_execute`)
   - Session events DB (analytics, metadata, resume snapshots) for ALL sessions in the project
   - Session events markdown file
   - In-memory session stats + persisted stats file
3. Call the `mcp__context-mode__ctx_purge` MCP tool with the chosen parameters:
   - Scoped: `{ confirm: true, sessionId: "<id>" }`, implies scope:'session'.
   - Project: `{ confirm: true, scope: "project" }`, explicit destructive form.
   - Bare `{ confirm: true }` still works but emits a deprecation warning. Prefer the explicit forms.
4. Report the result to the user, the response lists exactly what was deleted and (for scoped purges) confirms that other sessions and project stats were preserved.

## Schema rules

- `confirm: true` is always required.
- `sessionId` and `scope: "project"` together is REJECTED as ambiguous (the sessionId implies session scope; combining with project scope contradicts intent).
- `scope: "session"` without `sessionId` throws, sessionId is required.

## When to Use

The rest: https://github.com/mksglu/context-mode/blob/HEAD/skills/ctx-purge/SKILL.md