Agent Purge CLI
A CLI switches Markdown instruction profiles across coding agents and shows active integrations in a local dashboard
- 1,299 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The chosen adapter can modify global settings, PATH and client files; the README also mentions binary patching, so retain backups.
- Client updates can break compatibility or modified files. Test append outside a production project first.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/agent-purgeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The chosen adapter can modify global settings, PATH and client files; the README also mentions binary patching, so retain backups.
- Client updates can break compatibility or modified files. Test append outside a production project first.
This is third-party code. Review the repository files before installing.
What it does
Agent Purge stores Markdown instruction profiles and applies a selected profile when launching a coding agent. Users switch profiles from the terminal or local dashboard. Separate adapters apply the same text to different clients. It supports instruction addition, replacement and disabling. An adapter can pass launch arguments or write persistent settings. Other routes use a PATH wrapper or an in-session command. `agent-purge status` reports their state. A first trial can use a custom profile with Codex and explicit `--mode append`. This mode adds the selected rules to the original instructions. Replacement coverage and consequences depend on the adapter.
Who it is for. Teams using several coding clients and switching custom instructions between tasks while inspecting adapter settings.
Good fit when
- Switch custom task instructions without copying text
- Use one style profile across supported clients
- Inspect persistent, PATH-wrapper and session-command integration states
- Disable integrations and inspect remaining settings
Not a fit when
- You require a guarantee that instruction replacement preserves all built-in safeguards
- You cannot alter client settings or PATH command precedence
- You need identical behavior across client versions without adapter checks
- You cannot back up settings or use a test client for the first trial.
Example request
Prepare a concise technical-response profile for Agent Purge. Show how to launch Codex in append mode. Do not enable global integrations or binary modifications.Limitations
The CLI excludes optional Magpie from a separate subdirectory; installing the package does not add that plugin. Profiles default to ~/.agent-purge/, configurable through AGENT_PURGE_HOME. Some adapters modify global settings, PATH and client files; documentation conflicts on binary patching, so inspect the chosen mode. Byte-perfect restoration is not guaranteed; back up settings and recheck compatibility after client updates.
How to disable. Run agent-purge disarm --all, then inspect `agent-purge status`. This removes integrations and switches the global mode off. Check client settings and PATH before uninstalling the npm package. Delete personal profile data separately.
FAQ
Where are custom profiles stored?
Under `personas/` in `~/.agent-purge/` or the `AGENT_PURGE_HOME` location. `state.json` stores configuration. Inspect a profile before applying it.
How do I open the local dashboard?
Run `agent-purge web` for `http://127.0.0.1:7788`. It edits local profiles and integration state; do not expose it to a network without separate protection.
Can I only add instructions?
Yes. Use explicit `--mode append` for a launch. The default is read from saved state and can differ. Added instructions still affect model behavior.
How do I disable every integration route?
Run `agent-purge disarm --all`, then inspect `agent-purge status`. It removes integrations and turns the overall mode off. Review client settings separately.
Do I need my own agent account?
Yes. Agent Purge launches a client and changes instructions. Model access, payment, login and working-file permissions remain the client’s requirements.
What license does the CLI use?
MIT.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI that gives six coding agents project context, over 80 skills, verification and resumable tasks across sessions
A Rust coding agent with a native GUI, a terminal mode, an ACP mode for Zed and an MCP server
agentplay turns local Claude Code, Codex and Cursor sessions into a file map and a replayable step timeline.
Work modes for AI coding agents: a light solo mode for daily tasks and /man with a plan, checks and review for big changes
Session monitor for Claude Code, Cursor, Codex and six more agents in a terminal, window or HTTP API, with chat cleanup and search
Tasks, docs, specs and decisions live as markdown files in your repository, and the agent reads them through the CLI and MCP
README in short
Supported clients and integration methods are listed separately. The profile list and local dashboard report installed versions and available channels; the static capability table can lag behind runtime state.