christophevg / yoker / 33500781505

85%

push

github

feat(context): effective-configuration summary in environment reminder

Agents systematically under-see configuration: the effective config is
a merge of dataclass defaults, user TOML, project TOML, manifest and
CLI — but agents can only read fragments (e.g. not ~/.yoker.toml).
Config effects then surface as surprising tool behavior, costing
investigation rounds and sometimes producing false conclusions (a
per-target env-var allowlist from user-level config read as a
"guardrail bypass").

Add render_config_summary(): a curated, redacted summary of the
effective configuration embedded in the environment reminder:

- github allowed_operations (write ops explicitly granted vs read-only)
- make allowed_env_vars per target (deny-by-default phrased explicitly)
- git permission split (auto-approved vs approval-required)
- filesystem_paths, network_access, write-protection state
- backend provider + model (names only)
- trusted plugins

Security: redaction is structural — the renderer only reads an explicit
allowlist of fields, so credential fields (api_key etc.) are
structurally unreachable; a test proves a populated key never appears.
List caps with overflow notices keep the block within context budget.

Verified live: after session restart the summary appears in the
environment reminder and correctly surfaces the user-level
[tools.make] allowlist that was previously invisible to agents.

🤖 Implemented together with Yoker.

2979 of 3894 branches covered (76.5%)

Branch coverage included in aggregate %.

9120 of 10755 relevant lines covered (84.8%)

0.85 hits per line