Skip to content

Original Layout Forcibly Replaced with a Single-Conversation Context Interface #48888

Description

@GHZhi

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.

Activity

  1. github-actions commented on Sep 14, 2026

    @github-actions
    Contributor

    This issue does not fully meet our contributing guidelines.

    What needs to be fixed:

    • The bug report is missing required context: OpenCode version, Operating System, Terminal, and Steps to reproduce are all left as "No response"
    • There is no reproducible information — it is unclear what changed, what version introduced the new layout, or how to reproduce the issue
    • Please describe the expected vs. actual behavior in a structured way

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


    This issue might be a duplicate of existing issues. Please check:

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. aa2013 commented on Sep 14, 2026

    @aa2013

    The new layout is really hard to use. It's not nearly as good as the old one. The controls are completely counterintuitive, and the new layout is also missing features.

  3. 0-SamboNZ-0 commented on Sep 14, 2026

    @0-SamboNZ-0

    I also agree that the original layout was MUCH easier to use; this is a significant loss for usability!

  4. GHZhi commented on Sep 14, 2026

    @GHZhi
    Author

    At the very least, the session list on the left must be kept! Is Opencode actually not open at all? Who made this decision on behalf of everyone?

  5. github-actions commented on Sep 14, 2026

    @github-actions
    Contributor

    Thank you for updating the issue! It now includes all the required information — a clear description, steps to reproduce, screenshot, OS, terminal, and version. The needs:compliance label has been removed. We appreciate you taking the time to fill this out properly.

  6. AsiaM659 commented on Sep 14, 2026

    @AsiaM659

    The biggest missing feature for me is that with this new interface I can only drag and drop one file from the File Tree into a prompt.
    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.
    @GHZhi - can You add this to Your Issue description.

  7. aa2013 commented on Sep 14, 2026

    @aa2013

    使用 ai 写了个脚本锁定旧版本布局, 我本机测试通过了

    I used ai to write a script that locks in the old version layout, and it passed testing on my machine.

    #48882 (comment)

  8. GHZhi commented on Sep 14, 2026

    @GHZhi
    Author

    The biggest missing feature for me is that with this new interface I can only drag and drop one file from the File Tree into a prompt. 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. @GHZhi - can You add this to Your Issue description.

    Added...

  9. yimenglq commented on Sep 14, 2026

    @yimenglq

    This brand-new layout is complete trash, and I can't even tell the different workspaces apart in the project anymore. I'm seriously done.

  10. enngins commented on Sep 14, 2026

    @enngins

    Please give us old layout back!!!

  11. AsiaM659 commented on Sep 16, 2026

    @AsiaM659

    使用 ai 写了个脚本锁定旧版本布局, 我本机测试通过了

    I used ai to write a script that locks in the old version layout, and it passed testing on my machine.

    #48882 (comment)

    Thanks @aa2013 , this works perfectly for me

  12. davidlopezsalvador commented on Oct 8, 2026

    @davidlopezsalvador

    The forced single-conversation window drove me up the wall too. Workaround that restores the original layout on Windows Desktop:

    https://github.com/davidlopezsalvador/opencode-legacy-patch

    How it works: a same-length patch inside app.asar moves oldInterfaceSunset to 2099, so resolveNewLayoutDesigns(retired, ...) stops hard-coding the new layout, and app-update.yml is neutralized so the auto-updater cannot silently wipe the patch.

    • Tested on 1.18.34 -> 1.18.35 (Electron 42, Windows); applies with the app open in ~2 minutes; one-command rollback (-Mode restore).
    • Fail-safe: the script searches the literal dynamically and aborts unless it finds exactly 1 occurrence.
    • Caveats: Windows desktop only; updates frozen until you restore -> update -> patch (script included); unofficial, use at your own risk.

    I maintain the repo, feedback welcome. This is only a stopgap until a permanent official toggle ships.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions