anomalyco / anomalyco/opencode

bug(app): active sessions missing from sidebar in new UI

Open
#49,401 2 comments 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Sep 16, 2026.

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

Description

Description

After switching from the legacy UI to the new UI, the project sidebar shows no sessions in both Web UI and OpenCode Desktop. The same project and server showed the sessions correctly in the old UI.

A new session created in the new UI (test1111) also does not appear in the project list after returning to it.

Plugins

Reproduced in both Web UI and Desktop; not specific to a plugin.

OpenCode version

1.18.31

Steps to reproduce
  1. Run OpenCode in WSL: opencode serve --hostname 0.0.0.0 --port 4098.
  2. Connect to the server from the Web UI and OpenCode Desktop.
  3. Open the project at /home/master/projects/market-strategy-testing.loc.
  4. Create a new session.
  5. Return to the project/session sidebar.
Expected behavior

Active project sessions should be listed, as they were in the legacy UI.

Actual behavior

The project is selected, but the session list is empty in both Web UI and Desktop.

Diagnostics
  • GET /project returns the correct project and worktree.
  • GET /session?directory=<project>&roots=true returns active sessions, including the newly created session.
  • The session rows have time_archived = NULL.
  • Directly opening a session by ID works.
  • Therefore the sessions exist in SQLite and are returned by the API; only the new UI list does not render them.
Operating System

Windows 11 with WSL2

Related issues

Related to #27837, #36064, and #29766, but this report also reproduces in the Web UI and confirms that a newly created session is returned by the API.

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.