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
{{ message }}
Repository navigation
Regression since v1.4.8: startup can enter a blank/partially empty TUI state before real data is ready #23281
The unconditional return true makes the rest of the loading gate unreachable, so the UI can be considered ready before sync/bootstrap state is actually ready.
Together, these changes make it possible for the TUI to enter a session-like route too early, render while the real session/provider/workspace state is still not ready, and show a blank or partially empty intermediate state before the real elements appear.
Plugins
local plugin environment present
OpenCode version
1.4.11
Steps to reproduce
Start OpenCode
Wait for the UI to become usable
Observe that the UI first appears blank or partially empty, then fills in later
The issue does not use one of the three required issue templates (Bug Report, Feature Request, or Question). Please re-submit or edit this issue using the appropriate template — this looks like it should be a Bug Report, which requires a ### Description field, steps to reproduce, version info, OS, and terminal details.
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:
Thanks for updating the issue! It now includes all the necessary information — version details, steps to reproduce, and expected behavior. The compliance label has been removed.
Seeing the same, also cannot send any messages until its actually loaded which can take forever in a massive repo - just did a full reinstall of WSL because I thought I had broken something developing a plugin
Seeing the same, also cannot send any messages until its actually loaded which can take forever in a massive repo - just did a full reinstall of WSL because I thought I had broken something developing a plugin
I suddenly encountered this problem today. Before that, I had been using version 1.4.7 with my own session plugin, so I also assumed it was caused by my plugin. It wasn’t until I noticed that the version number in the lower right corner had already changed to 1.4.11 that I asked Codex to analyze the updated code, which is why this issue came up.
Activity
github-actions commentedon Apr 18, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
### Descriptionfield, steps to reproduce, version info, OS, and terminal details.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:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Apr 18, 2026
Thanks for updating the issue! It now includes all the necessary information — version details, steps to reproduce, and expected behavior. The compliance label has been removed.
PandaSt0rm commentedon Apr 18, 2026
Seeing the same, also cannot send any messages until its actually loaded which can take forever in a massive repo - just did a full reinstall of WSL because I thought I had broken something developing a plugin
CissiBot commentedon Apr 18, 2026
I suddenly encountered this problem today. Before that, I had been using version 1.4.7 with my own session plugin, so I also assumed it was caused by my plugin. It wasn’t until I noticed that the version number in the lower right corner had already changed to 1.4.11 that I asked Codex to analyze the updated code, which is why this issue came up.
PandaSt0rm commentedon Apr 18, 2026
Yeah just downgraded to 1.4.7 and its totally fine again
inschrift-spruch-raum commentedon Apr 18, 2026
Version 1.4.10 has the same issue.
CissiBot commentedon Apr 19, 2026
Fixed in 1.14.17, so I’m closing this issue. If it is still reproducible, please add more details and reopen it.