Lite is free. Pro adds this and the rest of the quality layer.
Adams forCloudflare projects.
Config files sit next to the code. Adams keeps tokens and account ids that should not be public out of them.
Lite and Pro
// the problem
What goes wrong
Config invites secretsIt is tempting to put a token into a config file to make a deploy work. That file is committed with everything else.
Edge code is hard to seeA function that runs at the edge has no local screen. A fault shows up in production logs, if you look.
// what adams does
What Adams does
Catches tokens in configLite: a token in a config or script is stopped at commit and moved to an ignored env file.
Reviews the functionPro: a separate agent looks at input handling and error paths in your handlers.
Writes down the setupPro: a handoff records bindings and settings you chose, so a new session does not guess.
// worked example
An example
A token in a config
Illustrative output.
~/project~/your-project · example
$
git commit -m "wire up deploy"adams: blocked
An API token in deploy.config.ts:8
Moved to .env, which git ignores
✓ Committed, no secrets found
// faq
Questions
Does Adams manage my Cloudflare account?
No. It reads local files only.
Can it check a deployed site?
Pro page checks accept a live address.
What is free?
Secret, git and leak guards.
// related