Config options documented but ignored: two agent-CLI bugs expose silent settings failures
Two separate bugs discovered this week in the agent-CLI ecosystem revealed configuration settings that appeared fully supported in documentation, schemas, and UI but were never actually read during execution. In iowarp/clio-coder, the settings context.compaction.model and context.compaction.systemPrompt were advertised across docs and the settings schema but ignored at runtime, silently falling back to defaults without any warning to the user. A fix was shipped in v0.4.3 roughly 90 minutes after the issue was filed, establishing a design principle that invalid or unread settings must fail visibly rather than silently revert. The second issue, still open in the openai/codex repository, involves a subtler problem where reading a single token-budget configuration key causes unrelated settings to lose their model-provided defaults entirely. Both cases highlight a broader software reliability concern: when configuration options are wired incompletely, operators have no way to know their intended settings are not taking effect.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in