fix(desktop): reduce update restart time

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[0x4bs3nt]

What Changed

• Pre-stage macOS updates during the download phase so the Restart action is only enabled once Squirrel has finished preparing the update.
• Show a clear “Preparing update…” state while the updater is taking over.
• Only force-destroy application windows on Windows, where NSIS requires it. macOS and Linux retain their normal quit lifecycle.
• Show an immediate startup splash when reopening after an update.
• Keep JavaScript dependencies inside ASAR on macOS and Linux while preserving the existing broad unpacking required for Windows WSL support.
• Continue unpacking native modules and executables such as Claude, node-pty, passkeys, ffi-rs, and fff.

Why

Restarting after an update could appear to do nothing for around 20 seconds or longer.

Most of that delay came from two bottlenecks:

1. Squirrel’s native update preparation did not begin until the user clicked Restart.
2. The packaged application contained roughly 14,500 unpacked files, all of which Squirrel had to process individually.

This change moves native macOS preparation into the download flow and reduces the unpacked application tree to 184 files in a test package. The remaining restart flow is primarily normal application and backend startup, while the user receives visible feedback throughout the transition.

The platform-specific behavior is preserved:

• macOS uses native pre-staging.
• Windows retains the unpacking and window shutdown behavior required by WSL and NSIS.
• Linux continues using its existing AppImage installation lifecycle.

UI Changes

• The update control now displays “Preparing update…” instead of appearing stuck at 100% downloaded.
• The update action is disabled while the updater is taking over, preventing duplicate restart attempts.
• The first launch after an update immediately displays a “Starting T3 Code…” splash while the backend reconnects.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes - not applicable
• I included a video for animation/interaction changes - not applicable

---

Note

Medium Risk
Changes core desktop update and quit/relaunch paths across platforms with new async coordination on macOS; behavior is heavily tested in this PR but regressions would affect all packaged users during updates.

Overview
Moves macOS Squirrel native staging into the download flow so Restart is only offered after electron.autoUpdater reports the staged app is ready, with a “Preparing update…” state instead of looking stuck at 100% downloaded.

Install/relaunch behavior now persists a one-shot relaunch marker before quitAndInstall, clears it on failed installs, shows a “Starting T3 Code…” startup splash when the marker is consumed, and only force-destroys windows on Windows (NSIS); macOS and Linux keep their normal quit lifecycle. autoInstallOnAppQuit is enabled only on darwin to drive native pre-staging.

Startup splashshowConnectingSplash takes a reason (wsl vs update-relaunch) and can refresh copy on an existing splash. Web update UI disables actions and shows “Preparing…” during staging and pre-install takeover.

^{Reviewed by Cursor Bugbot for commit ff79a9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Reduce update restart time by pre-staging macOS updates natively and showing a preparing splash

• On macOS, the update download now waits for the native Electron autoUpdaterupdate-downloaded event before completing, enabling OS-level pre-staging before restart.
• A persistent relaunch marker (DesktopUpdateRelaunch) is written before quit and consumed at startup to show a 'Starting T3 Code…' splash instead of a cold-boot splash.
• showConnectingSplash in DesktopWindow.ts now takes a ConnectingSplashReason ('wsl' | 'update-relaunch') and can refresh an existing splash in-place when the reason changes.
• UI surfaces (sidebar pill, settings button, tooltips) show a 'Preparing…' state during native staging via new isDesktopUpdatePreparing and isDesktopUpdatePreparingToInstall helpers.
• Behavioral Change: on macOS, windows are no longer force-destroyed before quit; on Windows the existing destroy behavior is retained.

^{Macroscope summarized ff79a9b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f15b82ea-3c3e-41f5-8006-165699eec1ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new macOS-specific native update pre-staging functionality, adding persistent marker files, deferred async coordination, platform-specific behavioral differences, and new UI states. These are significant runtime behavior changes to the update/restart flow that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16b01a9. Configure here.}

[macroscopeapp]

Reviewed against the Effect service conventions. One finding: a synthetic Error is manufactured only to satisfy a required cause on DesktopUpdaterReportedError, which also gives this locally-detected invariant a misleading updater-reported message. Everything else (namespace imports, make/layer shape, dependency acquisition via yield* Foo.Foo, scoped listener acquisition, catchTags usage) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}