Guard · Config

Config

Stop debugging env-var typos at 11pm - the Doctor finds them at noon. The full env-var registry plus a Doctor subtab that flags referenced-but-unset, missing-from-example, prod-unsafe, and declared-but-unused vars.

See it in motion

Where to find it

  • Desktop: http://localhost:4000/, then Guard → Config in the sidebar.
  • Hosted: desktop-only. The repoops.ai sidebar carries an “On the desktop app” pointer for it.
  • Keyboard: ⌘ K, then type “Config”.
  • On disk: .claude/brain/config.md + .env.example

What it does for you

Every env var the project reads, named once.Each row: who reads it, what happens when it's missing, whether it's required in prod. No more “is this used anywhere?”
The Doctor catches the four classic footguns.Referenced-but-unset (will crash at runtime), missing-from-example (new dev can't boot), prod-unsafe (localhost URL in prod), declared-but-unused (dead var lying around).
One source of truth: this file + .env.example.Add a new var → add it here AND to .env.example in the same PR. The Doctor flags drift.

Configure

The Doctor reads .env.example, your local .env, and the codebase. No setup - open the tab and it runs.

Use it well

Open the Doctor subtab before any deploy. Treat its rows as a blocker, not a warning. New env var → the rule is: read it in code, add to config.md with reader path + missing-var fallback, add to .env.example with a comment. Three places, one PR.

Read more