Files
platform/src/servers/api
pastilhasandClaude Opus 5 b07cae142f adopt on a resume even when the harness is a guess
Regression from my own B7 change, reported within the hour: turns collapsing to "turn
completed without output" and coming back only on refresh.

B7 stopped resume-cursor defaulting an unidentified session to claude-code. Correct for the
durable cut-off row, wrong for adoption: useChat sends model only if modelRef.current is
set, so a reconnect without one is routine, not exotic. Declining to adopt left the socket
unbound to the live session, so the running turn output went nowhere — and a refresh looked
like a fix because it rebuilds from the durable log.

Adoption is about DELIVERY and must be generous; only the durable write needs certainty. So
adopt on the default again, mark it as an assumption, and skip the cut-off check on it.
That keeps B7 fixed — no false "agent went away" written against an opencode session — with
no unbound sockets.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 17:03:17 +01:00
..
2026-08-04 14:20:52 +00:00
2026-07-25 23:30:20 +01:00
2026-08-03 00:28:51 +00:00
2026-02-26 17:42:59 +00:00
2026-08-04 03:24:15 +00:00
2026-02-25 07:27:30 +00:00
2026-02-16 19:34:35 +00:00