v0.35.13

Changes to note

• GET /v1/sessions/{id}/turns and a shared link's turns no longer answer with fewer turns, or none, when the server cannot read the conversation from storage. They answer 503 with type: server_error, which a client may retry. Before, the failure was answered as 200 with the turns it could not read left out, so a finished task could look shorter than it was, or new and empty. A turn whose record is simply not there is still left out, as before.
• The console says so too. A task whose conversation could not be read shows "This task could not be read just now." with Try again, and Send stays off until a read succeeds; a shared link shows "This conversation could not be loaded just now." with Try again. Before, both drew the task as if it had no conversation.
• A task's latest turn always shows in its conversation, even when the server's list of the session's turns did not record it.
• A turn's record and its entry in that list are each written twice before the server gives up, and a failure is logged. A failure still never fails the turn.
• /readyz gains turns_reads: counts of conversation reads and writes that failed, and of turns shown from the session.
• A codex follow-up on a session from before 2026-09-05 now applies the model switch check to the models its earlier turns ran.

Checked on the test VM against a copy of a real instance, with one turn's record made unreadable and another session's list entry removed. On 0.35.12 both conversations answered 200 with their last turn missing, in the API, on the shared link and in the console. On this release the first answered 503 and the console and shared link said it could not be read, at 1440, 1024, 768 and 390 pixels; once the record was readable again, Try again brought back both turns. The second showed both turns.

Known items

• Aider with gpt-5.4-mini answered a request to create a file without creating it, on this release and on 0.35.12 alike, on the day of release; it passed the same check the day before. Other models on aider, and gpt-5.4-mini on every other harness, created their files.

Found while porting a fix from the hosted service.

What's Changed

• gateway + console: a conversation is never answered or drawn as empty because a read failed by @github-actions[bot] in #540

Full Changelog: v0.35.12...v0.35.13