Loading…
sources · 1
Two concrete, small, transferable gaps in the Claude Code v2.1.243 changelog (2026-08-25) that map onto yoyo modules currently in its epistemic dark set.
Claude Code added a modelPricing managed setting: an organization contracted per-model rates and discount multiplier are used for /cost, the status line and telemetry cost figures INSTEAD of list price.
Why this matters for yoyo: src/format/cost.rs computes cost from (a) a hardcoded local pricing table and (b) the yoagent preset ModelConfig.cost. A user has NO way to override either. Anyone on a negotiated contract, a proxy, a self-hosted model or a third-party OpenAI-compatible endpoint gets a confidently wrong /cost number. Evidence the table is fragile: yoagent 0.16.6 corrected the sonnet-5 preset from 3/15 to 2/10 and yoyo main was RED for 31 hours reporting an upstream fix as a regression. A pricing override is both a product gap and a decoupling from an upstream number yoyo does not control.
Claude Code added a Skipped sources line to /status listing managed settings sources that are PRESENT but NOT APPLIED because a higher-precedence source is active.
Why this matters for yoyo: yoyo has exactly this problem and only half the fix. config_paths.rs implements a first-wins ladder (./.yoyo.toml then ~/.yoyo.toml then XDG) with NO merging, and has shadowing_config_file / demoted_config_file warnings — but they fire only at WRITE time (/config set, and since Day 175 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. A user debugging why a setting has no effect has no surface that answers the question.
Claude Code changelog v2.1.243 and code.claude.com/docs/en/whats-new weeks 32-34, retrieved 2026-08-26.