anomalyco / anomalyco/opencode

mod+shift+w and mod+o do nothing in the new layout

Open
#39,785 1 comment 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Jul 31, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

describe the bug

two keyboard shortcuts do nothing in the new layout, and their commands are missing from the palette:

  • mod+shift+w (new workspace) on the new session page
  • mod+o (open project) anywhere in the new layout

root cause

both commands are registered in exactly one place, packages/app/src/pages/layout.tsx, which only mounts inside LegacyServerLayout.

in Routes, the draft page is declared as a sibling of that tree rather than a child of it, and new layout session routes go through TargetSessionRoute, also outside it:

<Route component={LegacyServerLayout}>
  <Route path="/:dir" component={DirectoryLayout}>...</Route>
</Route>
<Route path="/new-session" component={DraftRoute} />

so in the new layout that shell never mounts, neither command is ever registered, and both keybinds resolve to nothing.

workspace.new had been registered on the draft page in c9a5556, but that was dropped when the page's commands moved into use-new-session-commands.tsx.

not a keybind matching problem. the command context only suppresses keybinds inside a contenteditable when no modifier is held, and both of these hold one, so the prompt editor never swallowed them.

steps to reproduce

  1. enable the new layout
  2. open the new session page
  3. press cmd+shift+w, nothing happens, the workspace chip stays on local
  4. press cmd+o, nothing happens, no directory picker opens

both commands are also absent from the command palette.

expected behavior

  • mod+shift+w sets the workspace chip to new workspace, same as picking it from the chip menu
  • mod+o opens the directory picker and opens the chosen project
  • both appear in the command palette under their categories

screenshots

(screenshots to be added)

environment

  • desktop app, dev build, new layout
  • macos

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.