Set up Fallow in Codex

1. Check the installation

fallow_check_install

{}

• If it reports a version, continue.
• If fallow is missing, explain that the app runs the fallow CLI locally and that no code leaves the machine. Offer to install it globally with

  npm install --global fallow

  . The sidebar dashboard needs a fallow on PATH, because the app runs a copy inside the project only within the Codex sandbox of a thread. Run the install only after the user agrees. Then call

  fallow_check_install

  again.

2. Choose the defaults

fallow_settings_read

{}

1. "Analyze the whole project by default, or only the files your branch changed?" Map the whole project to

   scope: "full"

   and changed files to

   scope: "changed"

   .
2. "Leave tests, stories and dev tooling out of the analysis?" Map yes to

   production: true

   .

fallow_settings_update

set

{"set":{"scope":"changed"}}

3. Run the first analysis

fallow_analyze

{}

fallow_analyze

4. Show what the app adds

• Fallow in the sidebar opens the full dashboard.
• Code Health opens beside a thread and follows the project of that thread.
• Type @Fallow in the composer to attach a finding or all findings of a rule.
• Open

  .fallowrc.json

  or

  .fallowrc.jsonc

  to edit rules and preview their impact before saving.

  .sarif

  files open in a findings viewer.
• Before a commit, ask Codex to audit the branch.

5. Offer the next step

.fallowrc.json

.fallowrc.jsonc

fallow.toml

.fallow.toml

fallow-setup