Skip to content

desktop: session hangs indefinitely in Working/Thinking after Oct 22 update (Bun runtime) #58786

Closed as not planned

Description

@lorenzo-chavez-antonio

Summary

After the desktop app updated on 22 Oct 2026 (runtime changed to Bun), chat sessions hang indefinitely showing "Trabajando"/"Pensando" (Working/Thinking) with no response and no error surfaced. It reproduces in brand-new sessions, so it is not a corrupted/oversized session.

Environment

  • opencode version: 2.1.4 (desktop). Note: OpenCode.exe --version was unusable because it launches the GUI and fails with Unable to move the cache: Acceso denegado.
  • OS: Windows_NT 10.0.26300 (win32 x64)
  • Terminal: Unavailable: desktop app, no TERM* environment variables are set.
  • Shell: C:\windows\system32\WindowsPowerShell\v1.0\powershell.EXE (as spawned by the agent); COMSPEC is C:\windows\system32\cmd.exe.
  • Install/channel: latest; desktop build updated 22/10/2026 09:25 (updater "pending" folder). Recent stack traces reference Bun paths (B:/~BUN/root/...).
  • Active plugins: none found in ~/.config/opencode/opencode.jsonc.

Reproduction

  1. Update the desktop app on Windows (update applied ~22 Oct 2026 09:25, Bun-based runtime).
  2. Open the app and start a new session.
  3. Select a model (tried opencode-go/hy4-preview and opencode-go/qwen3.8-flash).
  4. Send a message, or paste the results of an execution / a file path.
  5. The session stays in "Working"/"Thinking" forever; nothing is returned and no error appears in the UI.

Expected Behavior

The selected model streams a response, or OpenCode surfaces a visible error if the request fails.

Actual Behavior

  • The session remains in the Working state indefinitely with no output.
  • Sometimes instead the model emits an infinite repetition loop (same fragments repeated for many screens, e.g. "Wait, this PRE script: ICA_IC_DET_PRE.sql no..." or "Durante el proceso de back-and-forth..."), consuming context/tokens.
  • Pressing Stop sometimes leaves the turn stuck in Working; fully quitting and reopening the app does not reliably clear it.
  • opencode.log shows no ERROR for those turns, only INFO lines (e.g. spawning process for rg.exe / powershell.EXE). Related earlier errors include Failed to drain Session and free-usage-limit errors for the opencode free models.

Additional Context

  • Not a corrupted session: fresh tabs hang as well, and it happened in at least 2 differentsessions/tabs, incl. one whose earlier turns had worked.
    -Workarounds tried: abort the turn (Esc/Stop), fully quit + reopen the app, switch model, edit model in config. None helped consistently.
  • Frequency: consistent/repeatable in the current build (multiple occurrences on 24 Oct 2026).
  • Config (secrets redacted): "model": "opencode-go/qwen3.8-flash", same for small_model, no plugins configured.

Activity

  1. opencode-agent commented on Oct 24, 2026

    @opencode-agent
    Contributor

    Thanks for the detailed report! A session that hangs with no error can have several different causes, so a few details would help us narrow it down:

    1. Project folder: which folder is the session opened in? Is it a git repository, and roughly how many files does it have, including untracked or ignored ones? Is it your home folder, or inside a folder that has a .git higher up?
    2. Logs for one hung turn: the opencode.log lines from when you send the message until you press Stop (with secrets removed). Please include the full Failed to drain Session error and stack trace if it shows up.
    3. Other setups: does it also hang in a new session opened in a small, empty folder? If you can, does the CLI (opencode) or another provider/model behave the same?
    4. Which problem is most common: of the two problems, the endless hang and the model repeating itself, which happens most? Do both happen with both models?

    You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know you're done.

    These existing issues may be related, ordered by likelihood:

  2. KMThegamer2022 commented on Oct 27, 2026

    @KMThegamer2022

    i am getting the same thing

  3. opencodejr commented on Oct 28, 2026

    @opencodejr

    Thanks for the detailed report. A session stuck on "Working" with no error can have several different causes in v2, so we need a few more details to tell which one this is:

    1. Which folder did you open as the project? Is it a git repository? Roughly how large is it, and does it contain many untracked files (for example, is it your home folder or a folder full of generated data)?
    2. Does it also hang in a small, empty folder (for example, a new empty directory opened as the project) with the same model?
    3. Logs for one hung turn: the lines in opencode.log from the moment you send the message until a minute or so later. Please also include the full text of the Failed to drain Session error you mentioned, with its stack trace if it has one. Redact anything private.
    4. Optionally: does starting the app with the environment variable OPENCODE_DISABLE_FILEWATCHER=true change anything?

    You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.

    These issues may be related, ordered by likelihood, so you can check whether one of them already covers your problem:

  4. l3payy commented on Oct 29, 2026

    @l3payy

    The same thing...

  5. opencodejr commented on Oct 31, 2026

    @opencodejr

    We're closing this for now because we haven't heard back. Without the project folder details, the log lines for a hung turn and the full Failed to drain Session error, we can't tell what keeps the session stuck on "Working" in desktop 2.1.4.

    If it still happens, please reply here with those details and we'll take another look. Opening a new issue is fine too. In the meantime, #48657 (no response when the snapshot step stalls on a large untracked file tree) is the most likely match, so it's worth checking whether your project folder fits that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions