Files
orca/src
Brennan Benson d65d12b2fe fix(native-chat): say when a transcript is unreadable on this host instead of spinning
An agent running in an SSH worktree writes its transcript on the remote
machine, so the desktop resolves nothing and subscribeNativeChatTranscript
re-polls forever with no frame. The client's loading state only clears on a
stream frame, so the chat view spins indefinitely with no error (#13663).

Emit one advisory snapshot once an unresolved transcript passes a deadline.
It is deliberately non-terminal: the resolve poll keeps running and a later
real snapshot replaces it, so a session that is merely slow to flush its
first JSONL line still loads (#8401). The deadline is generous for the same
reason -- a late message costs less than a false one on a healthy session.

This lands in the shared subscribe path, so desktop, mobile, web and headless
all get it without a wire change; clients already render an error carried on
the snapshot frame.
2026-08-23 14:35:44 -07:00
..