Skip to content

chore: vendor Ponytail as repository-local Codex plugin - #10

Merged
bryanwieg merged 1 commit into
rx9070-portfrom
chore/integrate-ponytail-plugin
Sep 20, 2026
Merged

bryanwieg merged 1 commit into
rx9070-portfrom
chore/integrate-ponytail-plugin

Conversation

@bryanwieg

@bryanwieg bryanwieg commented Sep 20, 2026 •

Copy link
Copy Markdown
Owner

Vendors Ponytail's standard Codex plugin runtime into this repository and exposes it through a repository-local Codex marketplace.

Layout

  • third_party/ponytail/ - canonical project copy of the Ponytail plugin
  • .agents/plugins/marketplace.json - local marketplace exposing ponytail@llama-cpp-local
  • scripts/setup-ponytail.ps1 / .sh - install the local plugin through Codex
  • scripts/update-ponytail.ps1 / .sh - refresh the vendored copy from upstream
  • docs/agents/ponytail.md - integration/update documentation

Full Ponytail behavior retained

The vendored payload contains the upstream six skills and lifecycle hooks:

  • SessionStart activation
  • UserPromptSubmit mode tracking
  • SubagentStart propagation
  • lite/full/ultra/off modes
  • upstream default mode: full

The project does not reimplement or flatten Ponytail into ordinary .agents/skills; Codex still loads it as a real plugin.

Upstream provenance

Initial vendored revision:

DietrichGebert/ponytail@e3ba2aa6f1e6f0bc4d69eb09c9f0d0a93af56156

third_party/ponytail/UPSTREAM_REVISION records the source commit.

The executable hooks and skill files are copied unchanged. The only packaging adaptation is cosmetic: the local manifest uses Ponytail's upstream SVG logo rather than its large PNG.

Updating

Run the project updater, inspect the resulting hook/skill diff, then commit it. This makes executable plugin updates reviewable repository changes instead of consuming upstream main live.

Codex still requires the user to review/trust Ponytail's hooks through /hooks; the setup scripts do not bypass that security boundary.

Keep Ponytail's complete Codex runtime payload in third_party/ponytail and
expose it through the repository marketplace at .agents/plugins/marketplace.json.

The vendored payload preserves Ponytail's six skills and executable lifecycle
hooks so Codex runs the standard SessionStart, UserPromptSubmit, and
SubagentStart behavior, including full-mode default, mode persistence, and
subagent propagation. The only local packaging adaptation is cosmetic: use
Ponytail's upstream SVG logo instead of its large PNG in the manifest.

Record the exact upstream source revision, add setup scripts that install the
local plugin through Codex's normal plugin system, and add update scripts that
refresh the vendored runtime payload from DietrichGebert/ponytail main.

Ponytail updates therefore become explicit, reviewable repository changes
instead of loading unreviewed upstream main directly at runtime.
@bryanwieg
bryanwieg force-pushed the chore/integrate-ponytail-plugin branch from e9ab540 to 8079ec3 Compare September 20, 2026 05:20
@bryanwieg bryanwieg changed the title chore: integrate Ponytail through official Codex plugin chore: vendor Ponytail as repository-local Codex plugin Sep 20, 2026
@bryanwieg
bryanwieg merged commit b515e74 into rx9070-port Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant