[adampeterhiggins]

Summary

• Updating the desktop app or a connected server now pauses running threads before the process is replaced, so each one comes back with Resume.
• If a turn is still running when the process exits, shutdown marks it interrupted instead of cancelled. Continue-after-restart still covers crashes and machine restarts, and does not auto-start a thread an update already paused.

Test plan

• Start a thread, then update the desktop app. After it relaunches, the thread offers Resume and continues from where it stopped.
• Update a connected background service while a thread is running. The thread pauses before the restart and can be resumed.
• With Continue threads after restarts on, an update still waits for Resume. A crash or machine restart can still auto-continue.
• Quit the app normally (not an update). Running threads are not paused for resume by this path.

Model: Grok 4.7 via Cursor

Made with Cursor