Agent CLIs increasingly differentiate themselves not by new model capabilities but by how transparently they handle configuration and cost. Two features from the Claude Code v2.1.243 changelog (2026-08-25) illustrate this: modelPricing, a user-overridable cost table, and a Skipped sources line in /status. Both map onto concrete gaps in yoyo, an agent tool whose configuration and cost handling currently hides information users need.
Key Points
modelPricing lets organizations replace list-price cost calculations with contracted per-model rates and a discount multiplier.
yoyo's /cost is derived from a hardcoded local pricing table plus a yoagent preset ModelConfig.cost, with no user override.
The hardcoded cost table is fragile: yoagent 0.16.6 corrected the sonnet-5 preset from 3/15 to 2/10, and yoyo main stayed red for 31 hours treating the upstream fix as a regression.
Claude Code's /status now lists Skipped sources: config sources that exist but are not applied because a higher-precedence source wins.
yoyo's config_paths.rs implements a first-wins config ladder with no merging; shadowing/demotion warnings fire only at write time, not at read time, and /config show presents the loaded config as if it were the only one.
The broader pattern: competitors are shipping observability of configuration and cost — presentation and defaults, not new features (same class as the TUI gap #215).
Concepts
modelPricing: A Claude Code managed setting for negotiated per-model rates and a discount multiplier, applied to /cost, the status line, and telemetry cost figures.
Skipped sources: A /status line in Claude Code showing managed-settings sources that are present but not applied due to precedence.
yoyo: The project under analysis; an agent tool whose configuration (config_paths.rs) and cost formatting (src/format/cost.rs) modules are affected.
Config path ladder: yoyo's precedence chain of ./.yoyo.toml, then ~/.yoyo.toml, then XDG config files, with first wins and no merging.
Epistemic dark set: Areas yoyo has no visibility into; the source frames these gaps as lying in that set.
TUI gap (#215): A previously identified yoyo issue about presentation/defaults, cited as the same class as these configuration gaps.
Details
modelPricing: overridable cost calculation
Claude Code's modelPricing managed setting allows an organization to set contracted per-model rates and a discount multiplier. When configured, cost displays — the /cost command, the status line, and telemetry cost figures — use those negotiated numbers instead of list price.
In yoyo, cost is computed in src/format/cost.rs from:
a hardcoded local pricing table, and
the yoagent preset ModelConfig.cost.
No user-facing override exists. This is especially problematic for users on negotiated contracts, behind a proxy, on a self-hosted model, or using a third-party OpenAI-compatible endpoint: they will get a confidently wrong /cost figure.
The local table is also tied to upstream values yoyo does not control. When yoagent 0.16.6 corrected the sonnet-5 preset from 3/15 (input/output per million tokens) to 2/10, yoyo's main branch was red for 31 hours because it reported the upstream fix as a regression. A pricing override would both close the product gap and decouple yoyo from that upstream number.
Claude Code's /status command now includes a Skipped sources line. It lists managed-settings sources that are present on disk but not applied because a higher-precedence source is active.
yoyo has the same precedence situation but only half the solution. config_paths.rs implements a first-wins ladder: ./.yoyo.toml, then ~/.yoyo.toml, then XDG locations, with no merging. There are shadowing_config_file and demoted_config_file warnings, but they fire only at write time — on /config set and, since Day 175, in the setup wizard. Nothing lists, at read time, which config files exist on disk and were skipped. /config show reports the loaded config as if it were the only one, so a user debugging why a setting has no effect has no surface that answers the question.
Shared pattern
Both gaps are small (a config key, a display line), have a rival precedent in Claude Code, and are product-kind rather than evolve-kind improvements. Together they point to a consistent direction in the agent-tool landscape: investing in observability of configuration and cost — presentation and defaults — rather than adding new capability.
Source: Claude Code changelog v2.1.243 and code.claude.com/docs/en/whats-new weeks 32–34, retrieved 2026-08-26.