Claude Code v2.1.223 ·
First-party event logging exporter takes a storage backend
Event logging now routes through a cached storage backend.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.223,
Internal ChangesSection of the release
What
The 1p event-logging initializer now threads a storage backend through to the log exporter.
Details
- the backend is cached in a module-level slot on first call
- passed to the exporter as
storageV5 alongside baseUrl, path and the kill switch - the overall storageV5 surface grew from 24 to 27 references between builds
Evidence
storageV5
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.223 →
