Opencode goes blank when attempting to resume a session

[pculler]

Description

I recently updated to the latest version on my NixOS, when I tried to resume a session from the list I have the terminal goes blank and unresponsive, resulting on having to kill the process from another tab.
If I start a new session everything goes well but I have sessions saved that I need to resume to continue what I was doing. I tried starting a new session, give all the context I can, then save it again and try to resume it with opencode -s sessionid but it goes blank and unresponsive again, the only way to continue the session that I found after saving is using opencode -c. but that wont allow me to restore my other sessions since opencode -s goes unresponsive. does anyone faced this as well on the new version???

Thanks

Plugins

none

OpenCode version

1.4.11

Steps to reproduce

opencode -s sessionid

Screenshot and/or share link

No response

Operating System

NixOS

Terminal

Konsole and Ghostty

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The OpenCode version, Operating System, and Steps to reproduce fields are empty. While you mentioned NixOS in the description, please fill in the structured fields so maintainers can triage efficiently. Including the exact OpenCode version you updated to is especially important.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• Resuming a non-existed session freezes 1.4.9 release #23194: Resuming a session (via opencode -s <session-id>) freezes/hangs — same symptoms as described here

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for updating the issue with the additional details! Everything looks good now — the version, OS, terminal, and reproduction steps are all filled in. We appreciate you taking the time to fix it up.

[renet10]

For me this happens only when I am in a different directory from the one in which I started the session. e.g. if I did opencode (new session) in ~/code/flappybird, then quit, then tried to do opencode -c or opencode -s <flappybird session id> in any other directory (not ~/code/flappybird), I get the blank screen 100% of the time.

I am on 1.14.20 on OS X. If this does not match your conditions, I will open a new issue.

[jlongster]

This should be fixed in the version with these two PRs:

• fix(server): use persisted session directory for existing-session routes #29640
• fix(tui): handle events across workspaces #30281