anomalyco / anomalyco/opencode

Original Layout Forcibly Replaced with a Single-Conversation Context Interface

Open
#48,888 11 comments 4 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Sep 14, 2026.

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

Description

Description

My OpenCode layout has been forced into a window with only one conversation panel. So what am I supposed to do when I have lots of projects and conversations? Every time I have to click the fucking Home button in the top-right corner or press Ctrl+B? Who the hell came up with this idea? Your browser should be designed like this too—every time you fucking get to view only one session, and then you have to click a button to pop up a window where you can switch to other pages? I searched for ages and couldn't find the original window layout setting. Are you going to compensate me for the wasted time?

Plugins

no fking plugins

OpenCode version

v1.18.30

Steps to reproduce
  1. Start OpenCode with a workspace containing multiple projects and sessions.
  2. The left sidebar with the session/project list is no longer displayed.
  3. The layout is locked to a single conversation panel.
  4. There is no option in the settings to re-enable the legacy layout with the left sidebar.
  5. Switching contexts requires using the top-right Home button or Ctrl+B instead of clicking on the sidebar list.
Screenshot and/or share link
Image
Operating System

Windows 11

Terminal

PowerShell

Expected behavior
I expect the left sidebar (session/project list) to remain persistent, or at least provide a setting to restore the legacy multi-panel layout. Users should not be forced to click the Home button or press Ctrl+B to switch contexts in a single-window view.

Previously, it was possible to create complex prompts combining multiple data sources. There is also no way to use the File Tee in a new session—the button simply does not respond.

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.