Thread freezes after switching to Go model — requires Escape key to unstick #34460

Summary

After exhausting the free-tier quota and manually switching to a Go model, the thread becomes unresponsive / frozen. The only way to recover is pressing the Escape key, which unsticks the thread and allows interaction to continue.

Steps to reproduce

1. Use OpenCode with the default free-tier provider/model.
2. Exhaust the free-tier quota (hit the usage limit).
3. Manually switch to a Go model (e.g. via the model switcher).
4. Observe that the thread is now frozen — no input is accepted, the UI appears stuck.
5. Press the Escape key.
6. The thread unsticks and resumes normal operation.

Expected behavior

When the model is switched manually, the thread should remain interactive or immediately enter the new model's context without requiring a manual Escape key press to unstick.

Actual behavior

The thread freezes silently after the model switch. The user has no indication that Escape will fix it — it appears broken until the user happens to try Escape.

Environment

• OpenCode version: latest
• Platform: (add your OS / terminal)
• Provider: Free tier → Go model (manual switch)

Additional context

This seems to be a UI state issue where the model-switch event leaves the input handler in a stale or waiting state that is only resolved by an Escape keypress to reset focus or state.