Session list missing in TUI mode

[JohnYehyo]

Description

the session list displayed by the /session command in TUI is incomplete, but the list under the CLI command opencode session list is complete

As shown in the figure, only four sessions are displayed in TUI mode.

Additionally, I've checked related issues, and most similar problems state that TUI only displays sessions from the last 30 days. However, my case is different - as shown in my first screenshot in TUI mode, the most recent session is from March 25th, but when I check the session list under CLI mode, I have multiple recent sessions from March 27th and also several from March 25th that are not displayed in TUI mode.

Plugins

oh my opencode

OpenCode version

1.3.9

Steps to reproduce

No response

Screenshot and/or share link

Operating System

macOS 14.6.1

Terminal

Ghostty, iTerm2

[github-actions]

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

• TUI /sessions only show sessions from last 30 days, while CLI session list shows all my sessions (thank god) #16733: TUI /sessions only shows sessions from last 30 days while CLI session list shows all sessions (same TUI vs CLI discrepancy)
• TUI /sessions picker only shows recent sessions #13877: TUI /sessions picker only shows recent sessions (same root cause - implicit time/limit filter in TUI session listing)
• /sessions TUI only shows recent sessions, ignores historical ones #16270: /sessions TUI only shows recent sessions, ignores historical ones

These issues all describe the same underlying problem: the TUI /sessions command applies an implicit filter or limit that causes it to show fewer sessions than opencode session list does via CLI. Please review these issues and consider whether this is the same bug before proceeding.

[ohtyap]

@JohnYehyo I am experiencing similar issues, but I was able to narrow it down to the usage of worktrees. When I am running a session in a worktree, these sessions (even if the worktree is linked to the same project in the sqlite db) are basically lost.
Is this the same issue you are experiencing?

[OverHash]

@JohnYehyo I am experiencing similar issues, but I was able to narrow it down to the usage of worktrees. When I am running a session in a worktree, these sessions (even if the worktree is linked to the same project in the sqlite db) are basically lost. Is this the same issue you are experiencing?

Hi! I've been chasing down this bug. I've written the following in Discord:

I often have git worktrees for my project, so I'll have /project/, then Git worktrees of /project/.dmux/worktrees/a/.

Typically I'll be running OpenCode from cwd of the git worktrees, however in the past OpenCode would let me open those sessions even at /project/, which was very convenient.

This behavior no longer seems to be the case. Does anyone know what changed or why this may have changed?

This seems to match what you found. I investigated and found that rolling back to v1.3.1 and this is definitely a regression for me, the behavior works back there. It was supported in 1.3.3, and broke in 1.3.4.

I then got an LLM to investigate changes in 1.3.4 and came to the conclusion that @adamdotdevin had a change which appears to be the issue: https://github.com/anomalyco/opencode/pull/19288/changes#diff-4d007ffedbc7e49e787c5a936a9c0188f49e8ef495390101884117f06b91f9d0R76. I attempted to contact Adam in Discord but he has not responded so far. I asked the following:

Do you know if this was an intentional break in behavior for boosted performance? Or is this indeed a regression. By moving x-opencode-directory/x-opencode-workspace headers into URL query params, the GET /session endpoint treats that directory as an explicit filter in the db check (

opencode/packages/opencode/src/session/index.ts

Lines 751 to 753 in 71b2069

	if (input?.directory) {
	conditions.push(eq(SessionTable.directory, input.directory))
	}

), so my behavior of allowing sub-directory sessions is no longer supported.

Happy to contribute a fix if you think this is a break in behavior

edit: also just to mention that I am in the tui, though I think this was a change that was done for desktop performance based on what you work on?

.. and now I'm working on adding a regression test for this, under the assumption that it is a bug.

[OverHash]

The CLI works because opencode session list does not use the SDK/HTTP route at all (which is what broke in 1.3.4); it calls Session.list(...) directly:

opencode/packages/opencode/src/cli/cmd/session.ts

Line 93 in 1812130

const sessions = [...Session.list({ roots: true, limit: args.maxCount })]

[ohtyap]

Can confirm - works in 1.3.3 but is broken in 1.3.4 (and above)

From the linked commit, I agree, it sounds like a bug/not an intentional break. Thanks for the investigation!

To give also a bit of context, as I know from GitHub issues, there are several opinions on what sessions should be shown in the TUI: Currently, with this "bug", after closing the worktree, I have changes in my code base generated by the agent, but I can't access the sessions anymore that generated the changes in the first place. Of course, I could re-create a worktree with the same path, or extract the session based on DB queries directly - but I have to admit, having it in the TUI directly sounds more correct 😅

[OverHash]

Currently, with this "bug", after closing the worktree, I have changes in my code base generated by the agent, but I can't access the sessions anymore that generated the changes in the first place. Of course, I could re-create a worktree with the same path, or extract the session based on DB queries directly - but I have to admit, having it in the TUI directly sounds more correct 😅

I agree, this is the same problem that I have. I am frequently creating and deleting Git worktrees, however the sessions are still relevant for my entire project. Therefore, I prefer that the session picker lets me choose sessions that were created under worktrees.

In my case, it works quite well as I prefix session names with identifiers so I can 'choose' the correct session that way.

Also noting that OpenCode has had this behavior forever, so the change in behavior needs to be clarified by a maintainer if this is an intentional change OpenCode is making. obviously I'd be disappointed to hear so.

[JohnYehyo]

@JohnYehyo I am experiencing similar issues, but I was able to narrow it down to the usage of worktrees. When I am running a session in a worktree, these sessions (even if the worktree is linked to the same project in the sqlite db) are basically lost.我遇到了类似的问题，但最终发现问题出在工作树的使用上。当我在工作树中运行会话时，这些会话（即使该工作树链接到 SQLite 数据库中的同一个项目）基本上都会丢失。 Is this the same issue you are experiencing?你遇到的问题和这个一样吗？

In my case, it seems to be a different issue — I’m experiencing the same problem even when not using worktrees