Skip to content

[UI/UX Feedback] The old layout has been removed, but the new layout does not support multiple worktrees. 旧布局被强制移除,但新布局又不支持多工作树。 #48835

Closed as not planned

Description

@tp20c5

Description

As the title says, just now—around midnight on September 14—OpenCode Desktop suddenly switched to what’s being called a “new layout,” and the settings now show that “the previous layout is no longer available.”
However, the new layout doesn’t support multiple worktrees at all: you can’t select a worktree to create a session, and the session list doesn’t show which sessions belong to which worktree.
Is OpenCode planning to drop worktree support? That’s absolutely ridiculous.

Plugins

omo

OpenCode version

Desktop v1.18.30

Steps to reproduce

  1. Go to Settings > General > Layout
  2. Create a new session, YOU CAN‘T change the workspace
  3. Only the main branch/main workspace can be used👎🏻️

Screenshot and/or share link

No response

Operating System

centos7 for opencode serve,Windows10 for opencode desktop

Terminal

No response

Activity

  1. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

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

    If your issue is already covered by one of the above, please consider adding a "+1" or additional context there instead of opening a new report.

  2. tp20c5 commented on Sep 13, 2026

    @tp20c5
    Author

    This layout change severely impacts parallel development efficiency and has essentially degraded the desktop version back to a serial mode. As in #48837

  3. 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)

  4. changed the title [-]The old layout has been removed, but the new layout does not support multiple worktrees. 旧布局被强制移除,但新布局又不支持多工作树。[/-] [+][UI/UX Feedback] The old layout has been removed, but the new layout does not support multiple worktrees. 旧布局被强制移除,但新布局又不支持多工作树。[/+] on Sep 14, 2026
  5. tp20c5 commented on Sep 14, 2026

    @tp20c5
    Author

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

    棒!虽然旧布局还有不少bug,但至少能用。新布局不如改名叫教育版算了,还不如CLI多开方便😓️

  6. aa2013 commented on Sep 14, 2026

    @aa2013

    新布局不如改名叫教育版算了,还不如CLI多开方便😓️

    新布局实在是太难用了,简直反人类😓️不知道那个小可爱提出来的

  7. kire21b commented on Sep 14, 2026

    @kire21b

    +1 I hit this daily in my real workflow.

    Use case: monorepo with multiple apps, each in its own manually created worktree (wt-vela, wt-canalis, wt-mdl, etc.), each on a different branch, running in parallel.

    Issues I see in Desktop (v1.18.29):

    Manual worktrees are invisible, git worktree add creates wt-* directories, but Desktop doesn't detect them at all. I have to cd into each worktree and run opencode from CLI every time.
    Opening multiple worktrees replaces the existing project, all worktrees share the same git common-dir, so Desktop keys project ID by root commit hash. Opening wt-canalis silently replaces the wt-vela session I already had open (same root cause as #5638).
    No branch switcher in the UI, there's no way to switch branches without closing the session and reopening from CLI.
    What I'd like:

    Desktop should detect existing worktrees for the same repo (read the .git file in each worktree to find commondir)
    Show all worktrees as tabs within a single workspace, not as separate projects
    Add a compact branch indicator in the UI (worktree name + branch name)

  8. tp20c5 commented on Sep 15, 2026

    @tp20c5
    Author

    Manual worktrees are invisible, git worktree add creates wt-* directories, but Desktop doesn't detect them at all. I have to cd into each worktree and run opencode from CLI every time.

    In fact, the old layout supports recognizing manually created multiple worktrees. You need to select a session in the main partition of the target repository, close the desktop app, and then reopen it. In other words, the last session before restarting must be a session in the main partition—it cannot be a session in another worktree or another project.

    Furthermore, for a new worktree that has just been created and has no existing sessions, you do need to start a session from the CLI as a seed so that it can be recognized—for example, opencode run “hello”—and you can even terminate it before the token starts being consumed.

    This does require a bit of finesse. Although I’m not entirely sure why this is necessary, it does work.
    And the new layout is different, it doesn’t require any finesse because parallel worktrees simply aren’t possible.

  9. thdxr commented on Oct 11, 2026

    @thdxr
    Member

    Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

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