anomalyco / anomalyco/opencode
Desktop: new session page has no file tree (button absent) with New layout designs enabled
@Hona is already working on this.
Since Aug 12, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
When creating a new session in the OpenCode Desktop app, the file tree cannot be shown at all. There is no file tree button anywhere on the new-session screen.
With New layout designs enabled (the default), the desktop /new-session page renders only the prompt composer. The file tree (and its toggle button) do not exist on this page — not in the titlebar, not in the side panel. Expected: a way to open the file tree / project explorer for the session (button, toggle, or sidebar), like the old layout.
Repro
- Open OpenCode Desktop (latest, v1.18.x).
- Keep New layout designs enabled (default).
- Click "New session" (app routes to
/new-session). - Look for the file tree / project explorer or its toggle button.
Expected: file tree accessible (button visible or panel in the sidebar).
Actual: no file tree button exists at all; nothing to open the file tree.
Impact
Users on the new layout cannot browse the project in a session, making file references and navigation much harder.
Related
- #33119 — Desktop new-session page cannot toggle terminal (same class of issue:
/new-sessiondraft page renders only the prompt composer, missing panels mounted on the real session route) - #29951 — Advanced settings toggles for desktop toolbar buttons do nothing in new layout (V2 titlebar missing file-tree button)
- #34223 — File tree toggle hidden by desktop() gate in settings, panel not open by default
- PR #34828 — "fix(app): add file tree toggle to new session header" (appears related; user still cannot see it on latest release)
Environment
- OpenCode Desktop version: latest (v1.18.16)
- OS: Windows 11 64-bit
- Layout: New layout designs enabled (default)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.