Skip to content

chore: instruct the agent to add an env variable only for configurations #337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Stephen Belanger (Qard) merged 1 commit into from
Aug 26, 2026
Merged

chore: instruct the agent to add an env variable only for configurations #337

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
- Do not introduce new ad-hoc configuration reads via `std::env::var(...)` / `process.env` / `os.getenv(...)` in command logic.
- All user-facing/runtime configuration must be defined in `clap` arguments:
- a CLI flag, and
- a corresponding environment variable (`#[arg(env = ...)]`).
- for persistent configuration, a corresponding environment variable (`#[arg(env = ...)]`).
- Entry points/runners should receive configuration from the CLI layer (via args/env that the CLI owns), not from independent, undocumented env lookups.
- Extreme edge-case exceptions are allowed only when a flag is not feasible (for example, process-internal plumbing), and must be:
- documented inline with a short rationale, and
Expand Down
Loading