Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.311,
Internal ChangesSection of the release
What
In a remote session, the cloud worker running Claude Code uploads a stream of events about the session. Several parts of that upload changed.
Each internal event upload now carries the attempt number in a request header when it is known.
An upload with no sign-in headers now fails with a retryable error, "internal event POST not sent", instead of the general "internal event POST failed".
A 404 (not found) reply counts toward ending the session as gone only when the request was not to one particular excluded path.
Metadata reports drop repeats of values already recorded at start.
Writes of start rows, the first entries after a person's message, can wait up to a limit set by a startRowsMaxWaitMs flush policy.
Whether events are held now follows the policy the server sends, instead of eventHoldEnabled().
Once a marking result is uploaded, the worker reports model_turn_stored internal metadata.
Why
These are reliability changes inside remote sessions. Uploads that fail for lack of sign-in details are retried, and a stray not-found reply is less likely to end a session that is still alive.
