Find the official Ponytail GitHub repository
The project is DietrichGebert/ponytail on GitHub. It supplies instructions, skills and host-specific adapters that encourage a coding agent to reuse existing code and make smaller complete changes. It is not a standalone coding model. Start with that repository rather than an executable advertised under the same name.
This guide checks source revision 09c434ab73ca43761c5d8b0c5d341926c2fba710 on October 26, 2026. The package manifest and plugin manifests declare version 5.3.2. That identifies the inspected source; it does not establish the version already installed on your machine.
We reviewed public documentation and source files. We did not install Ponytail, execute its hooks, change agent settings or test an AI response.
Choose an integration before installing
The official installation guide distinguishes these routes:
| Route | What it supplies | Main limitation |
|---|---|---|
| Claude Code or Codex native plugin | Skills plus lifecycle hooks for activation and mode tracking | Requires a host that supports that plugin route and Node.js on the hook process's PATH |
| Skills CLI | Copies Ponytail's skills into the selected agent's skills folder | Copying skills does not provide the complete always-on plugin integration |
| Rules file | Instructions read by the host from its expected rules location | Does not provide the same plugin commands or runtime level switching |
Choose one route for the host you actually use. Layering a plugin, copied skills and copied rules can make it harder to tell which instructions remain active. Before any installation, save your existing configuration and read the proposed files and hooks.
Install the native plugin in Claude Code or Codex
For Claude Code, send the following as two separate prompts in the client, not as shell commands:
/plugin marketplace add DietrichGebert/ponytail
/plugin install ponytail@ponytail
The installation guide gives the same route for the Claude Code desktop app's Code tab.
For Codex, the repository documents these terminal commands:
codex plugin marketplace add DietrichGebert/ponytail
codex plugin add ponytail@ponytail
Then open /hooks in Codex, review the lifecycle hooks and trust them only if you accept what they run. Start a new thread. The guide says to restart the Codex desktop app after installation so it can pick up the plugin. The inspected Codex manifest identifies the skills directory and hook configuration.
These are the project's documented installation steps, not commands WebFV has tested against every host version. If your client does not recognize its plugin command, check that client's plugin support before changing unrelated settings.
Enable Ponytail and set its intensity
The Ponytail skill defines three levels. Lite carries out the request and names a smaller option for you to choose. Full is the default ruleset. Ultra also challenges parts of a request that the stated need does not justify. These levels do not authorize cutting security, validation, accessibility or requested work.
In Claude Code, use one command at a time:
/ponytail lite
/ponytail full
/ponytail ultra
/ponytail off
The README command reference says /ponytail reports the current level when active and enables the default level when off. In Codex CLI and the IDE extension, use namespaced skills: $ponytail:ponytail for the main skill, or $ponytail:ponytail-review for a diff review. Select the main skill and state the level you want rather than assuming Claude's slash syntax is identical in every client.
To choose the default for new sessions, merge this field into the existing Ponytail configuration instead of replacing other settings:
{
"defaultMode": "lite"
}
The configuration resolver checks PONYTAIL_DEFAULT_MODE first, then the configuration file, then falls back to full. The usual file is ~/.config/ponytail/config.json on macOS/Linux or %APPDATA%\ponytail\config.json on Windows. When set, XDG_CONFIG_HOME changes the configuration root. A valid environment override can therefore explain why editing defaultMode appears ineffective.
Use copied skills or rules deliberately
The documented Skills CLI route is:
npx skills add DietrichGebert/ponytail
Select the intended agent and installation scope. This copies skills; the installation guide says an always-on ruleset also needs a rules file or a plugin integration.
For a rules-only setup, use the matching file for your agent. Ponytail provides AGENTS.md and adapters such as .windsurf/rules/ponytail.md and .github/copilot-instructions.md. Preserve your project's existing instructions: merge the relevant guidance or use the host's supported additional file, rather than overwriting a customized AGENTS.md.
A copied rules file is not evidence that plugin hooks or commands were installed. Removing a plugin also will not remove rules you copied separately.
Troubleshoot the layer that failed
- Hook says Node is missing: check the non-interactive process's PATH. Node working in your terminal does not prove that a desktop-launched hook can find it.
- Codex skills appear but activation does not: revisit hook trust and start a fresh thread, as the installation guide directs.
- A command is unavailable: identify whether you installed a plugin, copied skills or only rules; then check the host's command namespace.
- The level keeps returning: inspect the environment override, configuration and remaining copied rules before reinstalling.
After changing one relevant setting, check one fresh session. Retain the host version, Ponytail version and a sanitized error if it still fails. Do not repeatedly install unrelated adapters to fix the same symptom.
Turn it off or uninstall it
Turning a mode off leaves the integration installed. For removal, the guide lists /plugin remove ponytail in Claude Code and codex plugin remove ponytail in a terminal for Codex. Rules-only users remove the specific copied file or merged section while preserving their other instructions.
Plugin removal can leave external state such as mode flags, configuration and statusline settings. If you want that state removed too, review the repository's cleanup script. The guide places cleanup before host removal because the script itself lives in the plugin. Back up settings first and locate the actual installed files; do not delete a whole agent configuration directory.
The README's code and token savings describe the author's particular benchmark. They are not a guaranteed result for your tasks or a WebFV measurement. Judge a trial by whether the change solves your task and preserves the checks it needs, not just by the number of lines removed.