CLI compatibility
The API rejects incompatible CLI contracts before performing an operation. Compatible releases continue working; an upgrade is required only when the contract changes. Older clients that do not report a contract version are also rejected.pullfrog watch or MCP process after upgrading. If the latest CLI still reports incompatibility, wait for the matching server deployment to complete and retry.
The CLI authenticates with the GitHub user signed in through gh auth login. Commands use the current repository’s GitHub origin unless an explicit scope is supplied.
Scope
--repo option (alias -R) selects one repository. The --org option selects organization defaults or a personal account’s shared settings. They cannot be combined.
Disabling a repository affects that repository only. Re-enabling does not install a missing workflow; use pullfrog init for setup.
Keys and values
keys and describe commands work offline. They describe the installed CLI’s supported keys, not the caller’s permissions. The authenticated list command shows write access and the source of each value.
Inherited defaults
When the repository has no model or effort override,get prints the organization default. With neither override set, model prints auto and effort prints 0.5. Unsetting a repository override restores inheritance.
These are configured defaults, not predictions of the next run. Trigger overrides, task flags, workflow environment, credentials, and funding can change runtime selection. Outside collaborators cannot read private org defaults; an inherited value reports unavailable to them.
Text and scripts
--file - to read text from stdin. Prompt edits affect only the named prompt. The environment allowlist uses one variable name per line.
Confirmations
Consequential changes prompt before writing: disabling a repo or its OSS subsidy, widening permissions or environment access, allowing non-collaborators or approving reviews, enabling auto-merge, and increasing automatic charging exposure. Ordinary edits and reductions do not prompt. Without a terminal, consequential writes require--yes. Enabling auto-merge also requires --ack-auto-merge; interactively, type MERGE. Confirmation never grants permission.
oss setting uses an existing funding grant; it does not enroll a repository. Enabling a grant can clear an incompatible model override, which the CLI reports. Signing and auto-merge remain subject to entitlement and runtime gates.
Secret names and values
set command prompts for a masked value or reads one from --file PATH (- for stdin). Secret values are not accepted as command arguments. Multiple names prompt for multiple values and save together, useful for custom provider credentials. File input accepts one name at a time. GitHub Actions secrets are separate; these commands manage Pullfrog’s secret store.
Subscription credentials use the existing provider flows:
Permissions
Personal-account owners have the corresponding organization-owner permissions. The GitHub token must also have access to the target. Suspended installations cannot be configured.