Subscriptions

Pullfrog can run on a plan you already pay for instead of API tokens. Claude, ChatGPT and Grok plans connect with one command, run from inside the repository, and Kimi and OpenCode Go issue an ordinary key.

SubscriptionConnect withGuide
Claudenpx pullfrog auth claudeClaude
Codex / ChatGPTnpx pullfrog auth codexCodex
SuperGrok or X Premiumnpx pullfrog auth grokGrok
Kimi membershipA KIMI_API_KEYKimi Code
OpenCode GoAn OPENCODE_API_KEYOpenCode Go

Each command stores the credential with Pullfrog, which is where it has to live.

Google AI Pro, Google AI Ultra and Muse Code plans can't pay for runs. Google's Antigravity terms bar using a consumer plan through products Google doesn't provide, and Google suspends accounts that do. A Muse Code subscription covers only Meta's own Muse Code client. Use a GEMINI_API_KEY, Vertex AI or a META_MODEL_API_KEY instead (see supported providers).

Usage limits

A subscription has usage limits, and runs on it fail until the limit resets. A second account or an API key for the same provider is a fallback.

When the provider says when the limit resets, Pullfrog re-runs each stopped review after that, if its pull request is still open. It re-runs up to five per reset, 15 minutes apart, so the reviews do not spend the new window at once.

Multiple subscriptions and fallback

Connect several Claude, Codex or Grok subscriptions by running the provider's auth command again.

npx pullfrog auth claude --org my-org
npx pullfrog auth codex --repo my-org/my-repo
npx pullfrog auth grok --org my-org

The CLI asks what to do with the connections already there:

  • Choose Add another to keep the existing connections as fallbacks, or Replace to swap one out once the new connection succeeds.
  • The account that signs in decides the result, and the CLI reports it: added, replaced, or reconnected when the sign-in was an account already connected.
  • A browser signs in as the account it already holds, so adding a second account takes a signed-out browser or a private window.

Each subscription card in the console lists its connected accounts. After a run checks a connection, its card shows Rejected if the provider refused it, or Limit reached with the reset time when the provider gives one.

Credential order

Before the agent starts, Pullfrog tries the credentials for the run's model and provider in this order:

  1. Keyless auth
  2. Subscriptions: the workflow's, then the repository's, then the account's, then shared personal ones
  3. API keys: the workflow's, then the repository's, then the account's

Within a scope, the most recently connected subscription goes first. A rejected or exhausted credential moves the run to the next one, so a fallback to an API key can incur API charges. If a provider cannot answer the check, Pullfrog keeps the current credential. Once the agent has started, Pullfrog does not switch credentials or models.

Personal subscriptions on organization repositories

The owner of a personal account can share one of its subscriptions with an organization or repository they also manage:

npx pullfrog auth list --org my-username
npx pullfrog auth share CREDENTIAL_ID --from my-username --repo my-org/my-repo
npx pullfrog auth unshare CREDENTIAL_ID --from my-username --repo my-org/my-repo

The list prints a binding ID for auth remove, a credential ID for auth share and auth unshare, and each connection's status: Rejected, Limit reached with its reset time, or - when the last check passed. Removing the connection from the personal account revokes its shares. Nothing is shared automatically because someone triggered a run.

© 2026 Pullfrog, Inc.

On this page