Skip to content

[FEATURE]: BRING BACK THE OLD LAYOUT #49021

Description

@wshalash

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The old layout for opencode was great for my workflow. Bring back the old layout!

Activity

  1. github-actions commented on Sep 14, 2026

    @github-actions
    Contributor

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

  2. wshalash commented on Sep 14, 2026

    @wshalash
    Author

    There is a good reason why this topic is a duplicate. I am adding my voice to the million others requesting the old layout back

  3. kmanderson12 commented on Sep 14, 2026

    @kmanderson12

    The recent change to force the new layout completely breaks the mental model that the previous layout encouraged. I no longer have easy visibility over which one of my projects has active agent activity. I'm left to try to infer the activity from the thread's title, which might not always be relevant or accurate. This adds friction and confusion that is completely unnecessary.

    The old layout needs to stay as a configurable option in order to support the workflows we've grown to love as we've used this tool.

  4. fpcxsun commented on Sep 15, 2026

    @fpcxsun

    Agree

  5. kuznecov-anatoliy commented on Sep 16, 2026

    @kuznecov-anatoliy

    Unofficial Windows build that restores the old layout while this gets
    sorted: https://github.com/kuznecov-anatoliy/opencode-old-interface — not
    affiliated with the team, just a stopgap. Full context and root cause:
    #49005

  6. Hona commented on Sep 16, 2026

    @Hona
    Member

    Have you seen the vertical tabs in the v2 branch?

    Image
  7. wshalash commented on Sep 16, 2026

    @wshalash
    Author

    these are not the same as the legacy layout where each project is essentially a workspace and within you have different tabs for different tasks. Regardless, I downgraded to a previous desktop version of OpenCode that doesn't have the new layout in.

  8. kmanderson12 commented on Sep 17, 2026

    @kmanderson12

    Have you seen the vertical tabs in the v2 branch?

    Image

    @Hona Here is what I find powerful about the legacy layout:

    • I can see all my projects at once. If there is agent activity in a project, it is immediately visible. And it is project-level context. In the new layout, I have to look at my open tabs and discern, “Wait is that the API or UI? What task was that? Did I close that thread I was working on?”
    • When I am working in a project, I am visually reminded that I am in that project. I don’t have to look up at the tab and try to discern, “What icon is that for? Is it the blue A or the red A?”. In the legacy layout, I immediately see the project name, path, and historical list of activity.
    • The list that I see on a project level is persistent, contextual, and immediate.
      • I don’t have to think about keeping a tab open because I might need to jump back in later. It’s automatically there and listed in a consistent, familiar way.
      • Because it’s a historical list of chat sessions, ordered by last updated, I can immediately see the recent context of what I’ve done in that project.
      • I don’t have to go Home to get this context. It is immediately there as I switch between projects. This means that when I’m actively working, I immediately have the project-level context I need.
        • In the new layout, the Home tab is adding an additional step that was unnecessary in the legacy layout.

    For example, here’s a scenario I just ran into:

    • A few days ago I did a code review on an open MR.
    • I closed that tab shortly after working on it.
    • Now, a few days later, I need to review some follow up changes.

    So, here are the steps I need to take to get back to that spot:

    New Layout:

    • Go Home
    • Click on the project
    • Scan through the list for a relevant title
    • Open the one that seems right.
      • If it’s the wrong one:
        • close that tab, back to home
        • scan the list again
        • open the right one.

    Legacy Layout:

    • Click the project
    • Scan through the list for a relevant title
    • When I click on one, I immediately see the chat (without “losing my place”)
      • If it’s the wrong one, just click another. It’s right there.

    So, with all that being said—
    For the short term, please consider maintaining the legacy layout as an option via settings.

    In the future, please remember that a layout enforces a mental model of how an application is used. Users who have grown to love their workflow with OpenCode are being forcibly removed from the mental model they learned and loved. This is causing friction, lack of productivity, and an increased mental load in a workflow that was once second nature.

    The legacy layout is powerful. Some version of this workflow should be carried into new designs.

    I really appreciate the great work the OpenCode team has done. This tool has been a true game changer for me. I want to continue to love it. I hope the team will consider this and many other similar requests. Thank you.

  9. davidlopezsalvador commented on Oct 8, 2026

    @davidlopezsalvador

    Same wish here. Until it comes back officially, this brings the old layout back on Windows Desktop without downgrading:

    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