Ctrl+O does not work on Windows desktop + two UI suggestions (input bar order, stop button)

Environment

• OS: Windows 11
• Device: Desktop
• App: OpenCode Desktop (Electron build)
• Screen reader: NVDA (I am a blind user and rely on it to use the app)

Bug: Ctrl+O does not open the project picker on Windows

This is the main problem I want to report.

The keybinding Ctrl+O is listed in the command palette for "Open project", but on the Windows desktop build nothing happens when I press it. On macOS it works as expected.

I did some digging and noticed a few things in the desktop code that may explain it:

• The application menu in the main process only exists on macOS. createMenu() returns early when the platform is not Darwin, so there is no menu to own a Ctrl+O accelerator on Windows.
• The menu item that maps to opening a project defines its accelerator only for macOS, with no Windows/Linux variant.
• The renderer registers the layout command with a mod+o keybinding (where mod maps to ctrl on non-Mac), but the key press does not seem to reach that handler on the Windows desktop build.

I could not determine the exact failing link, but from a user's perspective the shortcut simply does nothing on Windows. It would be great to register Ctrl+O for Windows/Linux desktop builds, for example with an Electron global shortcut or a keydown handler that reliably captures the combination.

Suggestion 1: Reorder input bar buttons

The input bar currently shows, from left to right: the stop button, then add images, then choose agent, then model selector.

It would be more ergonomic (and screen-reader friendly) to reorder them as: add images, choose agent, model selector, and stop last.

Keeping the stop button as the last element in the row separates action buttons from the send area and makes accidental presses less likely. For NVDA users, a stable and predictable order also makes tab navigation much easier to learn.

Suggestion 2: Stop button styling

The stop button currently has a yellow/orange glow and is circular. On a light background it is quite bright, and for someone who combines a screen reader with a little residual vision it draws attention away from more important elements.

A suggestion would be to use the theme's standard critical-action/danger color instead of the standalone yellow glow, and to keep the button shape consistent with the other input-bar buttons. Consistency in shape and color across the button row helps both visual and assistive-technology users build a reliable mental model of the toolbar.

Summary

1. Please fix Ctrl+O on Windows (and Linux) desktop builds — it is documented but not functional.
2. Consider reordering the input-bar buttons so the row ends with the stop button.
3. Consider toning down the stop button to match the theme and standard button shapes.

Thank you for the great tool. I am happy to provide more details or test builds if needed.