Skip to main content
Find any .prflow/config.json setting by name. Every setting PRFlow reads is listed here once, in alphabetical order, with the page that gives its type, accepted values, default and security note. Search this page for the key you have. If you are choosing settings rather than looking one up, start at Configuration.

How to Read a Setting Name

A name such as prflow_implement.stall_backstop.max_resume_attempts is a path through the JSON file. Each dot is one level deeper. Written out, that setting is:
Expected result: a stalled cloud implementation run is resumed at most twice. Every other setting keeps its default, because a key you leave out is a key PRFlow falls back on. A name containing <name>, such as providers.<name>.auth, means you choose that part yourself. It is the name you give your own provider entry.

Index

Not on This Page

Skill extensions are files, not settings. They live under .prflow/skill-extensions/ and are documented on Skill Extensions. Credentials are never settings. Store them as GitHub Actions secrets, described in Cloud Setup.

Read Defaults Correctly

The value the scaffold writes and the value an absent key falls back to can differ. /prflow:init writes prflow.effort: "low", while an absent prflow.effort falls back to high. Each family page names both whenever they differ, so read the fallback column rather than assuming the scaffolded file shows the default.
Unknown top-level keys are tolerated so that an older config keeps working after an update. Nested sections have closed schemas, so an editor flags an unknown key inside one. Cloud config loading checks that the file is valid JSON, but it does not run a full schema check.

A Setting Is Only Half the Answer

Some behavior is not configurable by a value at all: