ATTENTION DEFICIT · EP 005TOOL / PULLFROG

Pullfrog · now free for personal + open source

The agent moved into the repo. Tag @pullfrog.

Pullfrog is an open-source, model-agnostic GitHub bot from Zod creator Colin McDonnell. It listens for repo events — issues opened, PRs created, reviews submitted, CI failures — and runs coding agents inside your own GitHub Actions. On August 8 it went free for personal accounts and open source.

Public beta announced May 12, 2026; now generally available. Bring your own keys or use Pullfrog Router at raw provider cost with no markup — either way, compute runs on your Actions minutes and your model spend.

ONE ISSUE, NO TABSEVENT 0 · FILED
#412 · Flaky retry in sync worker
opened by you · just now
@pullfrog make a plan, then fix it
Quick Links posted: Make a plan · Implement
0

new interfaces to learn. Every step above happens as comments, branches, and checks in the repo you already have open.

The pond is the event loop

Follow one issue around the lily pads.

Every hop is a GitHub webhook event; every landing is an agent run in your own Actions. Scrub through a full plan → implement → review → fix cycle.

00 · ISSUE OPENED

You file it. Buttons appear.

Pullfrog posts Quick Links on new issues: Make a plan, Implement. Or tag @pullfrog in the body to start immediately.

01 · PLAN

The plan is a comment.

Iterate by replying — or just edit the plan comment directly yourself. When it reads right, hit Implement plan.

02 · IMPLEMENT

Branch, work, PR.

The agent runs against the latest version of the plan and opens a PR linked back to the issue.

03 · REVIEW

Review it like a colleague's PR.

It addresses comments and pushes updates. Batch with Fix all, or 👍 the comments you agree with and hit Fix 👍s.

04 · CI FAILS

It reads the logs and tries a fix.

With guardrails: skips bot-authored commits, only runs when the target branch is green, and rate-limits retries.

05 · MERGE

The merge stays yours.

Git and GitHub operations go through a permission layer — the agent can't push to protected branches.

ONE ISSUE · SIX HOPSEVENT: ISSUE OPENED
ISSUE#412 opened PLANas a comment PULL REQUESTbranch + work REVIEWyours + auto CI CHECKSwaiting MERGEhuman's call YOUR GITHUB ACTIONS webhook received: issues.openedpullfrog.yml dispatches the runkeys stay in GitHub secrets
ISSUE OPENEDYou file it; Quick Links buttons appear.
IN YOUR ACTIONSWebhook received; pullfrog.yml dispatches the run.
0 / 5
issueplanprreviewcimerge
WHO ACTSYou
WHAT HAPPENSIssue filed; Pullfrog posts Quick Links buttons
This traces the documented Plan → Implement → Review flow plus the self-healing behaviors. Automations are per-repo toggles — each trigger can be turned on, off, or given custom instructions from the console.
01 · NO NEW INFRA

It runs in your Actions, on your keys, with no new UI to learn.

Install the GitHub App, add one workflow file — pullfrog.yml — and Pullfrog can dispatch agent runs in response to webhooks. Keys live in GitHub's secret store, get auto-masked, and each run uses a short-lived installation token that's revoked when the run completes. Works with Anthropic, OpenAI, Google, Mistral, DeepSeek, OpenRouter — or an existing Claude Code or Codex subscription.

MODEL-AGNOSTIC

Switch models with a config change.

BYOK to any provider, or use Pullfrog Router — billed at raw provider cost with no markup — and skip key management entirely.

KNOW WHAT IT IS

A harness for CI, not your laptop.

McDonnell describes Pullfrog as a harness over OpenCode and Claude Code intended to run in CI. For local development, he says, just use those agents directly.

ISOLATION3 layers

shell in an isolated subprocess without sensitive env vars; git and GitHub ops through a purpose-built MCP server with permission checks; a built-in headless browser for E2E tests and screenshots.

STARS · AUG 15975

on pullfrog/pullfrog — early numbers for a GA tool. The landing page's "trusted by" row lists Remotion, Zod, and ArkType; Zod is McDonnell's own project.

02 · SELF-HEALING

Reviews get addressed and CI gets fixed without anyone re-triggering.

When someone reviews a PR Pullfrog created, it picks up the feedback and pushes updates on its own. When a check suite fails, it can read the logs and attempt a fix — on its own PRs by default, and optionally on human PRs it has reviewed.

THE GUARDRAILSBuilt to not chase its own tail.

Auto-fix skips bot-authored commits, only runs when CI is already passing on the target branch, and rate-limits retries to avoid runaway fix loops.

REVIEW ERGONOMICSFix all, or fix exactly the 👍s.

Batch-address a whole review, or react 👍 to the comments you agree with and Pullfrog applies only those, resolving the threads as it goes.

03 · THE PRICE MOVED

Free for people and open source. $30 flat for an org's private repos.

The August 8 pricing change dropped per-seat math entirely: personal accounts and public repos cost nothing, and an organization running Pullfrog on private repos pays one flat monthly fee no matter how many seats or repos.

As of August 8, 2026
Developer
Pro
Price
Free
$30/mo per account
Covers
personal accounts; open-source orgs on public repos
org private repos; flat — no per-run or per-seat billing
Extras
unlimited runs, members, and public repos
commit signing, issue indexing, observability dashboard

An Enterprise tier is listed as coming soon. "Free" still meters elsewhere: agent runs consume your GitHub Actions minutes and your model tokens (or Router balance) either way.

The agent didn't get a new interface. Your repo became one.