anomalyco / anomalyco/opencode

[UI feedback] Forced V2 interface destroys productivity for multi-project/multi-agent workflows (20+ sessions)

Open
#48,837 5 comments 18 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Sep 13, 2026.

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

Description

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
Describe the problem

As of today, the option to switch back to the old GUI is completely gone ("你現在使用的是新版面 先前的版面已無法使用"). This forced update has severely disrupted my daily development workflow.

My Workflow & Pain Points

I manage a heavy, multi-project environment where I run more than 20 sessions simultaneously.

  1. AI Agent Delegation Broken: I treat each persistent session as a distinct "AI Employee" assigned to specific tasks. In the old interface, having them constantly visible in the sidebar allowed me to easily orchestrate and delegate tasks across different AI workers.
  2. Top Tabs Layout is Unusable: Moving these 20+ sessions into top tags/tabs makes it extremely difficult to track, read, and manage. It creates massive visual clutter.
  3. Multi-Project Blindspot: I need to work on multiple projects at the same time. With the new hidden/tabbed UI, I completely lose sight of what is happening in other projects and sessions.

The new interface might look "clean" for casual users, but for power users with 20+ active tasks, it is a massive regression in usability and speed.

Suggested Solution

Please bring back a layout option or a configuration toggle to permanently pin the persistent sessions panel to the sidebar, just like the old interface. Power users need structural visibility, not forced simplicity.

Image

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.