How to Install Ponytail on Various Platforms: A Complete Guide for AI-Augmented Development Environments

To install Ponytail across Claude Code, GitHub Copilot, Gemini CLI, and 10+ other platforms, use host-specific CLI commands or configuration edits that load the ruleset from AGENTS.md and hooks from the hooks/ directory.

Installing Ponytail on various platforms involves selecting the appropriate installation path for your specific AI-augmented development environment. The DietrichGebert/ponytail repository distributes the plugin as a modular ruleset that integrates with Claude Code, Codex, Copilot CLI, and numerous other agents. While each platform uses distinct CLI syntax or marketplace commands, every installation ultimately converges on the same core artefacts: the AGENTS.md ruleset, the hooks/ directory lifecycle scripts, and the skills/ directory utilities.

Claude Code and Codex Installation

Both Anthropic platforms use a two-step marketplace registration pattern. According to the source code, these commands must be executed separately to properly register and install the plugin.

Claude Code uses slash commands within the chat interface:

/plugin marketplace add DietrichGebert/ponytail
/plugin install ponytail@ponytail

Codex (Claude Codex) uses the external codex CLI:

codex plugin marketplace add DietrichGebert/ponytail
codex plugin add ponytail@ponytail

After executing these commands, restart the Codex desktop application to ensure the lifecycle hooks located in hooks/ponytail-activate.js are properly loaded.

GitHub Copilot CLI Installation

The Copilot CLI follows the same marketplace pattern as Codex but uses the copilot command prefix:

copilot plugin marketplace add DietrichGebert/ponytail
copilot plugin install ponytail@ponytail

In interactive Copilot sessions, you may also use the slash equivalents /plugin marketplace add and /plugin install. Once installed, Copilot automatically injects the ruleset before each LLM turn.

Pi Agent Harness Installation

The Pi agent harness bypasses marketplace registration in favor of direct repository cloning:

pi install git:github.com/DietrichGebert/ponytail

This command clones the GitHub repository directly into the Pi harness, which subsequently auto-discovers and loads the hooks/ and skills/ directories without additional configuration.

OpenCode Installation

OpenCode supports two installation methods: npm-style registry references or local file loading. Edit your project's opencode.json to include:

{
  "plugin": ["@dietrichgebert/ponytail"]
}

Alternatively, load from a local checkout:

{
  "plugin": ["./.opencode/plugins/ponytail.mjs"]
}

The entry point at .opencode/plugins/ponytail.mjs registers the /ponytail commands and injects the ruleset at the active level, exposing mode switches for lite, full, ultra, and off.

Gemini CLI and Antigravity CLI Installation

Gemini CLI installs the repository as a Gemini extension:

gemini extensions install https://github.com/DietrichGebert/ponytail

Antigravity CLI (identified as the future Gemini CLI iteration) uses similar syntax but interprets commands as plain chat messages:

nagy plugin install https://github.com/DietrichGebert/ponytail

Both methods reference the gemini-extension.json file and load the ruleset each session, exposing /ponytail commands in the slash menu or as text prompts (/ponytail-review).

Qoder Installation

Qoder requires manual file placement rather than CLI commands. Copy the ruleset into your project:

cp .qoder/rules/ponytail.md $PROJECT/.qoder/rules/

For full plugin-tier support including lifecycle hooks, add the hooks configuration to your global settings:

jq '.hooks += {"ponytail": "hooks/qoder-hooks.json"}' $HOME/.qoder/settings.json > tmp && mv tmp $HOME/.qoder/settings.json

Hermes Agent Installation

Hermes uses a single install command with an enable flag:

hermes plugins install DietrichGebert/ponytail --enable

After restarting Hermes, the agent injects the active Ponytail mode before each LLM turn and exposes skills using the ponytail:<skill> namespace (e.g., ponytail:review).

Devin CLI Installation

Devin simplifies installation to a single command:

devin plugins install DietrichGebert/ponytail

Post-installation, skills become available as /ponytail:ponytail, /ponytail:ponytail-review, and other variants defined in skills/ponytail/SKILL.md.

Grok Build Installation

Grok Build requires explicit trust flags during installation:

grok plugin install DietrichGebert/ponytail --trust

This enables the plugin in ~/.grok/config.toml under enabled = ["ponytail"]. Skills appear as /ponytail, /ponytail-lite, and other mode variants.

Alternative Platforms: CodeWhale, Swival, and OpenClaw

CodeWhale requires no CLI installation; simply copy AGENTS.md into your project root or run codewhale from a checkout of the repository.

Swival uses a two-stage global-to-local installation:

swival skills add --global https://github.com/DietrichGebert/ponytail
swival skills add ponytail

Swival reads AGENTS.md both globally (from ~/.config/swival/library) and locally, activating skills with a $ prefix (e.g., $ponytail-review).

OpenClaw installs from ClawHub:

clawhub install ponytail

This generates skill files under .openclaw/skills/ponytail/ based on the repository's plugin.json manifest.

Core Installation Components

Every installation method—regardless of platform—converges on three critical artefacts from the DietrichGebert/ponytail repository:

• AGENTS.md – The master ruleset containing plain-text instructions that drive Ponytail's always-on behavior.
• hooks/ directory – Contains ponytail-activate.js and ponytail-runtime.js, which inject the ruleset at the start of each LLM turn and handle mode switching.
• skills/ directory – Houses the six command-level utilities: ponytail, ponytail-review, ponytail-audit, ponytail-debt, ponytail-gain, and ponytail-help.

Because every host merely loads these files, the installation remains platform-agnostic; the only variation lies in the host-specific CLI syntax used to fetch and enable the plugin.

Practical Configuration Examples

GitHub Copilot CLI Quick Start:

copilot plugin marketplace add DietrichGebert/ponytail
copilot plugin install ponytail@ponytail

After installation, invoke /ponytail ultra in any Copilot chat to switch to the most aggressive mode.

OpenCode Local Development Setup:

{
  "plugin": ["@dietrichgebert/ponytail"]
}

Place this in opencode.json at your project root. The system automatically injects rules at every turn.

Qoder Manual Rule Activation:

cp .qoder/rules/ponytail.md $PROJECT/.qoder/rules/

Optional global hooks configuration ensures lifecycle management across all Qoder sessions.

Summary

• Fourteen distinct platforms support Ponytail installation, including Claude Code, Codex, GitHub Copilot CLI, Pi, OpenCode, Gemini CLI, Qoder, Antigravity, Hermes, CodeWhale, Swival, Devin, OpenClaw, and Grok Build.
• Two primary patterns exist: marketplace CLI commands (Claude Code, Copilot, Devin) and file-based configuration (Qoder, OpenCode, CodeWhale).
• Three core artefacts power every installation: AGENTS.md for rules, hooks/ for lifecycle management, and skills/ for command utilities.
• Restart requirements apply to Codex and Hermes to properly load hooks/ponytail-activate.js.
• Mode switching is available on all platforms via /ponytail, /ponytail-lite, /ponytail-full, or /ponytail-ultra commands.

Frequently Asked Questions

What files does Ponytail actually install on my system?

Ponytail loads three core components from the DietrichGebert/ponytail repository: the AGENTS.md ruleset, JavaScript hooks under hooks/ (including ponytail-activate.js and ponytail-runtime.js), and skill definitions under skills/. Depending on your platform, these may be cached locally, cloned into a plugin directory, or referenced directly from the GitHub repository.

Can I use Ponytail without a marketplace or CLI plugin manager?

Yes. Platforms like Qoder and CodeWhale support manual installation by copying AGENTS.md directly into your project directory. OpenCode also allows loading from a local checkout by referencing ./.opencode/plugins/ponytail.mjs in your opencode.json configuration, bypassing npm registries entirely.

How do I verify that Ponytail is active after installation?

Send the /ponytail or /ponytail-help command in your agent's chat interface. If installed correctly, the system will respond with available mode switches (lite, full, ultra, off) and skill options. For CLI-based agents like Hermes or Devin, check that ponytail:<skill> completions appear in your command suggestions.

Do I need to restart my IDE or agent after installing Ponytail?

Restart requirements vary by platform. Codex and Hermes explicitly require a restart to initialize the lifecycle hooks in hooks/ponytail-activate.js. Claude Code, Copilot CLI, and Devin typically activate immediately upon installation completion. Check your platform's specific documentation in the repository's README for confirmation.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}