Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

Remote session rows and failures show detail from the post-turn summary

Remote session rows and failure reasons now use the post-turn summary's status detail, recent action and needs-action fields

Group of 2 You'll notice Improvements
JSON All of v2.1.296
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release

What

After each turn, a remote session (one running on another machine, which you watch or control from here) can produce a short post-turn summary. That summary is now used in more places:

  • Failed sessions: the reason shown now comes from the summary's status_detail, falling back to "the last turn failed". Before, it always read "the last turn ended in an error".
  • Session rows in the remote-agent and fleet views: they now use the status_detail, recent_action and needs_action fields of post_turn_summary.
  • No summary yet: the row's detail falls back to the repository and branch, then to "no summary yet".
  • Summary text is cleaned before it is shown. It must contain at least one letter or digit and must not start with [ede_diagnostic].
  • The length limit for matching tool names grew from 64 to 128 characters.

Why

You get a specific reason when a remote session fails instead of a generic one. The session rows also show what each session has been doing and whether it needs you.

See this entry in the whole of v2.1.296 →

Feedback