steveandClaude Opus 4.8
77bc672c19
Build image / build-and-push (push) Successful in 9s
The worst finding is one I created two commits ago: the server's `warning` field — added precisely because a failed save was being swallowed — was never read by the client. The "I couldn't save this exchange" message went nowhere, which recreated the exact silence the warning existed to break. It's wired now, and SSE frames are validated with zod rather than type-asserted, so the next field added server-side fails loudly instead of vanishing. Aborting during the initial fetch reported "Could not reach the server." The read loop already knew an abort was the caller's own doing; the request path did not, so pressing Stop looked like the network had failed. Unmount no longer aborts an in-flight turn, and that one is a design bug of my own making: selecting an object auto-switches the rail to the inspector, so clicking the canvas mid-turn silently killed the turn — while the canvas is exactly what you're meant to be watching. The request continues, the exchange is persisted server-side, and coming back to the tab shows it. Stop still aborts, but only our READ: the turn keeps running server-side either way, which is why its work still lands in History. /capabilities reported cfg.Agent.Ready() while the routes require NewRunner to have succeeded. A configured-but-unresolvable model would therefore advertise a chat tab whose first message 404s. It reports the runner's actual state now, and is a named handler like everything else in that file. A failed history load rendered as an empty conversation, which looks like the thread was lost — a much worse thing to believe than "it didn't load". Both the loading and error states are shown, and a failed "Start over" says so. Per-step refresh refetched the change history and the conversation, neither of which can move until the turn commits: up to 2×(N−1) requests per turn for data that cannot have changed. Split into a canvas-only refresh for steps and a full one for the end. describeUndo had its own copy of totalChanges' summation; it uses the helper, which now accepts an optional counts list. React.ReactNode became an imported ReactNode, matching every other component. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01H3zbym8Doka2d7D48maSgZ