-
Notifications
You must be signed in to change notification settings - Fork 0
Command uninstall and purge
Two irreversible maintenance commands. Both are gated: on a TTY they prompt for
confirmation; when scripted (non-TTY) they require --yes (or --force) or
refuse. Each names exactly what it removes and suggests exporting first — run
export before either.
columbus uninstall [--yes]Removes Columbus from the project entirely: deletes .columbus.json and the
whole project data directory (database, logs, exports). The repo's source is
untouched.
$ columbus uninstall --yes
uninstalled columbus project proj_2fd171eebe922fad
removed config: /your/project/.columbus.json
removed data: ~/Library/Application Support/columbus/projects/proj_…columbus purge [--yes]Clears all records from the database and resets .columbus.json to defaults,
keeping the project alive (same project_id). Files stay; data is gone. Re-run
columbus reindex to rebuild the index afterward.
$ columbus purge --yes
purged all data for project proj_2fd171eebe922fad
fresh db: ~/Library/Application Support/columbus/projects/proj_…/columbus.sqlite
config reset to defaults$ columbus purge # non-TTY, no --yes
error [USAGE]: About to erase all records in … — this is irreversible;
re-run with --yes to confirm (export first with `columbus export`)0 success · 2 usage (no confirmation / aborted) · 3 not initialized. See
Exit Codes.
Columbus — the navigator your coding agent has been missing · local-only, deterministic code context · Repository · Issues · MIT License
Getting started
Concepts
Guides
- Using Columbus with Your Agent
- Searching Effectively
- Navigating Code
- Project Memory
- Tracking Work: Epics, Stories & Tasks
- Keeping the Index Fresh
Command reference
Reference
- Output Modes
- JSON Contract & Errors
- Exit Codes
- Configuration
- Supported Languages
- Color & Environment
Project