Action shortcuts recorded in the browser are never saved #18427

Bug

In a browser client (hosted or local web) with settings:write, you can record a shortcut in a project action's Keybinding field, both in Settings → Project → Actions and in the chat's action editor. Saving reports success and the action is saved. But the shortcut is never written. Reopening the editor shows the old or empty shortcut.

Cause

Both save paths skip all keybinding writes outside Electron:

• apps/web/src/components/settings/useProjectScriptSettings.ts: if (!isElectron) continue; before the shortcut upsert/remove loop
• apps/web/src/components/ChatView.tsx: changesKeybinding requires isElectron, and if (!isElectron) return updateResult; returns before the keybinding write

The editor itself doesn't apply that gate, so the field is editable in the browser and its value is silently dropped.

Question for maintainers

Keybindings live in the environment's keybindings.json and the RPCs already check settings:write. The gate was kept deliberately in #15394 ("with the electron guard preserved"), but the reason isn't written down. Which direction is intended?

1. Browser clients may set action shortcuts. Remove both isElectron gates; the existing scope checks still apply. A reference implementation with focused tests (browser and Electron paths) is on saphid:t3code/sweep/action-shortcut-browser.
2. Shortcuts are desktop-only. Then disable or hide the Keybinding field outside Electron, so the browser doesn't offer a setting it won't save.

Happy to open a PR for either once the direction is clear. (Related, already open: #18412 fixes desktop saves deleting an unchanged shortcut when another field is edited.)

Found during an agent-driven audit (GPT-6.1 Sol), with the fix explored by GPT-6.1 Sol and reviewed by Claude Opus 5.5 in T3 Code. Filed by Claude Opus 5.5 in Claude Code via T3 Code on behalf of Alex Southwell.