docs: mark security.require_env as decorative in config.yaml#480
Merged
Conversation
No production code reads require_env (verified repo-wide grep; it's mirrored only in tests/conftest.py's mock-config shape). CLAUDE.md already documents this as a known agent-facing trap, but an operator reading config.yaml directly had no way to know the key is inert. Comment-only change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a comment above
security.require_envinconfig.yamlnoting that no production code reads it.Why / benefit
Verified via repo-wide grep:
require_envappears nowhere in production code, only mirrored intests/conftest.py's mock-config shape as part of the test fixture surface.CLAUDE.md§4 already documents this as a known agent-facing trap ("assuming the server refuses to boot withoutGROK_API_KEY...security.require_envis decorative — no code reads it"), butconfig.yamlitself carried no comment saying so — an operator reading the config file directly had no way to know the key is inert.Risk to monitor
None — comment-only change, no key/value touched, no behavior change.
yaml.safe_loadconfirms the file still parses andrequire_envstill resolves to["GROK_API_KEY"].Scan context
CyClaw-Optimize (ponytail + Karpathy + fable-protocol loaded). Finding #6 of an 8-finding scan; deduped against open PRs #473, #477, #415.
Generated by Claude Code