OpenCode Desktop freezes at startup? Separate repository and plugin checks.
A blocked startup view does not establish that Git loading or a plugin is at fault. Preserve the worktree, record the startup stage, then test one configuration variable in a disposable project.
Different symptom: OpenCode terminal hangs after loading a plugin.
Source checked 13 September 2026. Superpowers report #2252, opened 4 September, describes startup hanging on Windows with Superpowers 6.3.0 and OpenCode 1.18.27. The reporter isolated the plugin configuration. This does not establish that the Desktop Git-loading issue above has the same cause, or that every installation is affected.
- Record OpenCode and plugin versions, enabled integrations and the last startup log entry. Preserve configuration before changing it.
- Close the affected process. In a disposable test project, compare startup with the same configuration except for the suspected optional plugin being disabled through its documented configuration.
- Change one variable at a time. If startup works only without that plugin, report the comparison upstream; it narrows the cause but does not prove a permanent fix.
- Restore the original configuration after testing. Do not clear session history, delete project files or weaken permissions as a startup workaround.
We have not independently reproduced this report. If startup succeeds but progress later freezes, use the separate background-work diagnostics before repeating edits.
What the failure looks like.
OpenCode Desktop becomes unresponsive while loading the repository or review panel, especially on large worktrees with generated or vendor content.
Why it happens.
Synchronous Git change loading and a large review surface can block the UI thread before a normal session starts.
Fix it without losing the task.
What the next AI should receive.
OpenCode and plugin versions, OS, repository size and scope, enabled plugins, last startup log entry, disposable-project comparison, and current worktree diff.
Check before restarting
Separate repository loading from extension/plugin startup. Record OpenCode and plugin versions, then reproduce once in a disposable project before changing the real worktree configuration.
Boundary of the evidence
The cited OpenCode and plugin reports describe particular versions and setups; they do not show that every Desktop startup freeze has one cause.
Diagnostic checkpoint
Use a disposable repository to test one optional plugin or repository-scope variable; keep the real worktree untouched.
How ShardStitch helps.
ShardStitch can preserve local project changes and the last startup evidence before you isolate a plugin or repository-size factor. It cannot diagnose the Desktop process without logs or make a plugin change safe by itself.
Source trail.
OpenCode issue #29078 and the OpenCode documentation.
FAQ.
Should I disable every OpenCode plugin when Desktop freezes?
No. Preserve the active setup and test one suspected integration in a disposable project. A single-variable comparison is more informative and easier to undo.
Does an OpenCode startup freeze prove my repository is damaged?
No. The UI may be blocked during repository or plugin loading while project files remain intact. Check the worktree and startup logs separately before making changes.
Scope note: Evidence boundary: the linked issue reports and reproduction conditions are version-specific. A configuration comparison can narrow a cause but is not a confirmed general fix.