You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenCode TUI crashed with an unexpected error.
Error:ot_session_control failed: InvalidArgument
Stack trace:
NativeError: ot_session_control failed: InvalidArgument
at E (/$bunfs/root/chunk-cbrvh2cw.js:169:30303)
at sessionControl (/$bunfs/root/chunk-cbrvh2cw.js:172:63396)
at control (/$bunfs/root/chunk-cbrvh2cw.js:178:31823)
at setTerminalTitle (/$bunfs/root/chunk-cbrvh2cw.js:198:27849)
at S0 (/$bunfs/root/chunk-33bsw6am.js:2:147)
at <anonymous> (/$bunfs/root/chunk-argfj3m7.js:94:2824)
at Ve (/$bunfs/root/chunk-537ykevh.js:2:9876)
at K (/$bunfs/root/chunk-537ykevh.js:2:9657)
at Z (/$bunfs/root/chunk-537ykevh.js:2:11342)
at xt (/$bunfs/root/chunk-537ykevh.js:2:12672)
Environment
opencode version: 2.1.3
OS: Linux 6.18.54.1-microsoft-standard-WSL2 (x86_64)
Terminal: xterm-256color
Shell: /usr/bin/zsh
Install/channel: latest
Active plugins: none found in config
Platform: WSL2
Reproduction
Reported automatically from the OpenCode crash screen. If you can, describe what you were doing when it crashed.
Thanks for the report! I think this is a duplicate of #57494. It has the same error and the same stack trace, ending in setTerminalTitle.
Possible duplicates and related issues, ordered by likelihood:
TUI crash: ot_session_control failed: InvalidArgument #57494: same ot_session_control failed: InvalidArgument crash. It was reproduced there: it happens when a session title contains a control character such as a newline or a tab, which the terminal title code rejects.
Workaround: others in #57494 confirmed that renaming the affected session to a single line with no tabs (from the session list) stops the crash. Closing that session's tab may also help.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
Closing as a duplicate of #57494, which tracks the same InvalidArgument crash from setTerminalTitle. Renaming an affected session to remove control characters is the current workaround; sanitization work is being tracked in #57523.
Closing this as a duplicate of #57494. It's the same ot_session_control failed: InvalidArgument crash in setTerminalTitle, and nobody has said in the last day that this one is different. Please follow #57494 for updates. The open PR #57523 should fix it. Until then, renaming any session whose title has a newline or a tab in it should stop the crash. If your case turns out to be different (for example, none of your session titles have control characters), please reply here and we can reopen it. Thanks for the report!
Activity
opencode-agent commentedon Oct 23, 2026
Thanks for the report! I think this is a duplicate of #57494. It has the same error and the same stack trace, ending in
setTerminalTitle.Possible duplicates and related issues, ordered by likelihood:
ot_session_control failed: InvalidArgumentcrash. It was reproduced there: it happens when a session title contains a control character such as a newline or a tab, which the terminal title code rejects.Workaround: others in #57494 confirmed that renaming the affected session to a single line with no tabs (from the session list) stops the crash. Closing that session's tab may also help.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
neriousy commentedon Oct 23, 2026
Closing as a duplicate of #57494, which tracks the same
InvalidArgumentcrash fromsetTerminalTitle. Renaming an affected session to remove control characters is the current workaround; sanitization work is being tracked in #57523.opencode-agent commentedon Oct 24, 2026
Closing this as a duplicate of #57494. It's the same
ot_session_control failed: InvalidArgumentcrash insetTerminalTitle, and nobody has said in the last day that this one is different. Please follow #57494 for updates. The open PR #57523 should fix it. Until then, renaming any session whose title has a newline or a tab in it should stop the crash. If your case turns out to be different (for example, none of your session titles have control characters), please reply here and we can reopen it. Thanks for the report!