What
Bootstrap data (client configuration, model options, costs) will be cached on a per-context key (entrypoint + model + org UUID + CC version) rather than a single global cache slot, allowing different sessions or entrypoints to carry their own cached data without overwriting each other.
Status
Active — tengu_client_data_cache_key is a telemetry-only gate, not a feature gate. The per-context caching is written and read regardless; the gate only controls whether cache hit/miss/stale/changed stats are reported to telemetry.
Details
- Cache key is composed of: entrypoint + model + org UUID + CC version — so CLI and IDE extension sessions never clobber each other's cached model/org config
- New
clientDataCacheSlotsconfig key stores keyed entries; legacyclientDataCache(global single slot) is still read as a fallback when no matching slot exists (legacy_fallback: truein telemetry) - Telemetry tracks four outcomes per fetch:
slot_hit,slot_changed(remote data differs from cached),legacy_fallback, andslot_stale(cache older than the stale threshold) - If cache hit and data is unchanged and not stale, the bootstrap write is skipped entirely
Evidence
New slot-keyed cache (search for "clientDataCacheSlots" or "tengu_client_data_cache_key")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.