fix(desktop): preserve main window bounds

[anirudhsama]

What Changed

Persist the desktop main window position and size across launches.

Move and resize updates are debounced. Maximized windows save their normal bounds, and fullscreen bounds are ignored. Saved bounds are restored only when the complete rectangle fits within a currently connected display; otherwise, the app uses the existing 1100 x 780 default size and lets Electron choose the position.

Why

The desktop app currently creates every main window with fixed dimensions and no persisted position, so restarting resets the user's window layout.

Fixes #1829.

Verification

• 344 desktop tests passed
• vp run typecheck
• vp check
• Regression coverage includes minimized Windows bounds and shutdown write flushing
• Manually tested size and position restoration after a clean quit and relaunch on a physical macOS device

Checklist

• This PR is small and focused
• I explained what changed and why

Note

Preserve and restore main window bounds and sidebar width across sessions

• The desktop app now saves the main window's position, size, and maximized state to settings on move/resize/maximize/unmaximize/close (with a 500ms debounce) and restores them on next launch if they fit within a connected display.
• A new flushMainWindowBounds method on DesktopWindow is called during shutdown to ensure bounds are persisted before the app exits.
• The web sidebar width is restored from local storage on load, clamped to valid min/max bounds, and the CSS variable is hydrated via useLayoutEffect to avoid a flash of the default width.
• resolveInitialMainWindowBounds falls back to DEFAULT_MAIN_WINDOW_SIZE when persisted bounds don't fit any connected display, and logs a warning when display detection fails.

^{Macroscope summarized c28dfce.}

---

Note

Low Risk
Localized desktop window/settings and web layout UX; no auth or data-path changes, with fallbacks when display lookup or bounds validation fails.

Overview
The desktop app persists main window position, size, and maximized state in DesktopAppSettings, restores them when opening the main window (only if the saved rectangle fits a connected display), and flushes pending bounds on window close and app shutdown via flushMainWindowBounds in DesktopLifecycle.

Bounds updates are debounced on move/resize/maximize; maximized, fullscreen, and minimized windows save normal bounds. Invalid or off-screen saved geometry falls back to defaults without overwriting disk until the user moves the window.

The web shell applies the stored thread sidebar width on first paint (threadSidebarWidth helpers + --sidebar-width on SidebarProvider, with useLayoutEffect hydration in the sidebar rail) to avoid a width flash on load.

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

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[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

Run ID: 7d187606-e1a0-42ec-8ebf-72b306d8f130

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 window bounds persistence functionality with significant runtime behavior changes across settings, window lifecycle, and UI state management. Two unresolved review comments identify potential bugs (stale sidebar max width, race condition with maximized state). New features with substantive logic and unresolved findings warrant human review.

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

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[cursor]

Stale sidebar max width

Medium Severity

The sidebar's maxWidth is calculated once using window.innerWidth but doesn't update when the window resizes. This causes the sidebar to remain capped at an outdated maximum width if the browser window grows, preventing it from being expanded further.

 

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

[cursor]

Maximized fallback races persistence gate

Medium Severity

fallbackWindowMaximized is taken from persisted settings while the deferred maximize() runs only later on reveal, after move/resize/maximize listeners are already registered. Until that restore finishes, live isMaximized() disagrees with the baseline, so scheduleBoundsPersist can treat startup restore events as a user change and overwrite unrestorable saved bounds.

Additional Locations (1)

• apps/desktop/src/window/DesktopWindow.ts#L634-L637

 

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

[anirudhsama]

Thank you!