Windows desktop local sessions can hang/terminate on exact-file tasks (glob NotFoundError / undici terminated) #26180

Description

On Windows Desktop 1.14.40, local sessions against a repo that contains both CLAUDE.md and .claude/* can repeatedly hang or fail even when the user gives an exact absolute file path.

In my case the target file was:
D:\BNS\BunkerProject\TableTools\XLSX\Slot.xlsx

Observed behavior inside OpenCode was inconsistent but always stayed inside the planner/tool/runtime path instead of completing the requested file task:

• auto-read CLAUDE.md
• auto-read .claude/system.md
• auto-read .claude/spec.md
• earlier runs tried skill(table-tools)
• later runs called glob(**/Slot.xlsx) even though the user had already supplied the exact path
• later runs bypassed Excel MCP and started shell-level ZIP/XML parsing of the xlsx internals
• failures then surfaced as one of:
  • service=server error=NotFoundError failed
  • AbortError: Aborted
  • AI_APICallError with ECONNRESET
  • TypeError: terminated from undici / TLSSocket.onHttpSocketClose

This does not look like a model-only problem. The same task pattern is stable outside OpenCode with the same model family, while OpenCode keeps failing in intermediate planning/runtime layers.

Plugins

No plugin appears required to reproduce this exact bug.

The machine had historical plugin load failures from oh-my-opencode / opencode-antigravity-auth, but the reproductions above still occurred after disabling those problematic paths and after restarting the app.

OpenCode version

OpenCode Desktop 1.14.40

Steps to reproduce

1. On Windows Desktop, open a repo that contains a root CLAUDE.md plus .claude/system.md and .claude/spec.md.
2. Start a local session with openai/gpt-5.4.
3. Ask OpenCode to operate on an exact file path, for example:
   D:\BNS\BunkerProject\TableTools\XLSX\Slot.xlsx
4. Make the request explicitly say not to inherit old context and to inspect the current file contents first.
5. Observe that OpenCode still auto-loads repo instruction files and may choose extra discovery/planning steps such as skill(...), glob(...), or shell detours instead of using the provided path directly.
6. After one or more of those detours, observe one of these failures:
   • service=server error=NotFoundError failed
   • AbortError: Aborted
   • AI_APICallError with ECONNRESET
   • TypeError: terminated in undici

Screenshot and/or share link

Relevant local evidence from logs and sessions:

• Session ses_1fdec0041ffexMS1ywSKsx9oGn

  • read .claude/system.md
  • read .claude/spec.md
  • then glob(path=D:\\BNS\\BunkerProject, pattern=**/Slot.xlsx)
  • corresponding sidecar log contained only repeated:
    • service=server error=NotFoundError failed

• Session ses_1fde8c7f6ffepAajQn17yEYH12

  • successfully ran local shell checks against Slot.xlsx
  • then sidecar log ended with:
    • TypeError: terminated
    • stack includes Fetch.onAborted / undici / TLSSocket.onHttpSocketClose

• Earlier log also showed:

  • AI_APICallError
  • cause ECONNRESET
  • URL https://api.openai.com/v1/responses
  • model openai/gpt-5.4

These were observed in:

• C:\Users\<user>\.local\share\opencode\log\2026-05-07T105425.log
• C:\Users\<user>\.local\share\opencode\log\2026-05-07T105838.log
• C:\Users\<user>\.local\share\opencode\log\2026-05-07T034524.log

Operating System

Windows 11 x64

Terminal

OpenCode Desktop embedded local runtime on Windows

Expected behavior

When the user already provides an exact absolute file path, OpenCode should:

1. use that path directly,
2. avoid unnecessary glob / skill / repo-spec detours,
3. avoid inflating the request with large incompatible repo instruction files unless actually needed,
4. complete the session or fail with a clear actionable error, instead of hanging or terminating mid-stream.

Actual behavior

Windows desktop local sessions repeatedly hang or fail before the intended file task completes, with the failure point moving between planner/tool/runtime layers.

Related issue

This may overlap partly with #21979 on the stream termination side, but this report also includes the Windows local exact-path / glob / repo auto-injection behavior that appears earlier in the chain.