Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
Internal ChangesKind: in v2.1.315,
What probably matters to youSection of the release
What
In remote sessions, which run Claude Code in the cloud while you watch from another client, the client shows the conversation as rows of a transcript. Claude Code now keeps track of rows the client has not received yet:
A new ledger records the time spans during which rows are still owed to the client. It saves them as client_rows_owed in the session's stored details and resends rows for the spans that remain.
Spans that have been retried the maximum number of times are dropped.
The ledger is used through a guardsClientRows option controlled by a server-side switch, tengu_patient_ledger, which falls back to off when the server sends no value. Which sessions get it is decided on the server.
The client now tracks owed rows (clientRowsOwed). While any rows have been resent, urgent control requests no longer jump ahead in the queue. Before, they jumped the queue whenever a session was not holding across model calls.
When a release arrives carrying assistant or user rows, the whole-turn hold now ends earlier.
Why
The aim is that a remote session's transcript is not left missing rows, for example across a restart, and that urgent requests do not overtake rows being resent. It is controlled from the server, so you may not see any difference.
