fix(desktop): open home on editor escape

[ComputelessComputer]

Treat bare editor Escape as a main-shell home shortcut while preserving Escape handling for visible editor popovers.

---

Note

Low Risk
Keyboard and tab-navigation UX only; no auth, data, or payment paths. Behavior is covered by new unit tests.

Overview
Escape now consistently navigates to the home tab from the session title field and from a bare ProseMirror editor, while still letting mention and slash-command menus own Escape first.

The main-shell handler is refactored: home/chat logic lives in a shared useMainEscapeShortcutAction that reads latest tab state via useTabs.getState() (fixes stale closures). The capture-phase listener no longer bails on every defaultPrevented event—it uses shouldSkipEscapeShortcut, which still runs home for data-main-escape-target (title) and for .ProseMirror unless a data-editor-escape-consumer popup is in the DOM. TitleInput calls the same action on Escape and marks the input with data-main-escape-target; mention/slash popups are tagged as escape consumers. Tests cover these cases.

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

[netlify]

✅ Deploy Preview for old-char canceled.

Name	Link
🔨 Latest commit	9ab78f6
🔍 Latest deploy log	https://app.netlify.com/projects/old-char/deploys/6a19b21c261f3f0008673141

[cursor]

Cursor Bugbot has reviewed your changes 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 357719e. Configure here.}

[cursor]

Escape shortcut fires twice from title input

Medium Severity

When Escape is pressed in the title input, runEscapeShortcut executes twice. The title input's handleKeyDown calls it directly, AND the window capture listener's setTimeout also calls it because shouldSkipEscapeShortcut returns false for elements with data-main-escape-target. Both mechanisms independently trigger the same action. For chat close, this sends duplicate CLOSE events since chat.mode in the useCallback closure hasn't changed between the synchronous and asynchronous calls.

Additional Locations (1)

• apps/desktop/src/shared/useTabsShortcuts.tsx#L238-L253

 

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