{"version":"2.1.296","anchor":"remote-control-session-failed-state-shows-a-real-reason","canonical_anchor":"remote-control-session-failed-state-shows-a-real-reason","heading":"Remote session rows and failures show detail from the post-turn summary","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/remote-control-session-failed-state-shows-a-real-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Remote session rows and failures show detail from the post-turn summary\n\nRemote session rows and failure reasons now use the post-turn summary's status detail, recent action and needs-action fields\n\n**What**\n\nAfter 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:\n\n- 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\".\n\n- 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`.\n\n- No summary yet: the row's detail falls back to the repository and branch, then to \"no summary yet\".\n\n- Summary text is cleaned before it is shown. It must contain at least one letter or digit and must not start with `[ede_diagnostic]`.\n\n- The length limit for matching tool names grew from 64 to 128 characters.\n\n**Why**\n\nYou 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.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}