Large file read gets stuck, cascading to block all project conversations until a new independent session is opened

[BlessedChild]

Summary

When Finch is reading a large file, it gets stuck indefinitely (Fig 1). During this stuck state, opening other conversation windows within the same project also keeps spinning (Fig 2). Force-closing and reopening the app leaves it stuck in a perpetual loading state (Fig 3). Only opening a brand new independent conversation restores normal functionality, after which old projects also recover.

Steps to reproduce

1. Trigger a large file read operation in a conversation (e.g., ask Finch to read a large document).
2. Observe that the operation gets stuck with no progress (Fig 1).
3. Try opening other conversation windows in the same project - they also keep spinning (Fig 2).
4. Close and reopen the app - it stays in loading state (Fig 3).
5. Open a completely new independent conversation - it works normally.
6. Return to the old projects - they now work again.

Expected behavior

Large file reads should either complete, show a progress indicator, or timeout gracefully with an error message. The stuck state should not cascade to block other conversations or persist across app restarts.

Actual behavior

A large file read blocks the entire application. Other conversations spin indefinitely. The loading state survives app restart. Only creating a completely new independent conversation breaks the deadlock.

Screenshots

Suggested fix

• Implement a timeout for file read operations.
• Ensure that a stuck conversation does not affect other conversations' ability to function.
• Clear stale loading states on app startup.

Environment

• App: Finch 1.4.4 (1169) — Desktop
• OS: macOS 26.4.1 (25E253)