win10 opencode desktop breakdown every several hours

[nillwyc]

1. what happend

OpenCode 服务器每次开几小时就无法连接本地服务器。

2. 我查的Windows 系统事件日志
   如下：

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <TimeCreated SystemTime="2026-04-15T12:43:39.3983342Z" />
    <Channel>Application</Channel>
    <Computer>PC</Computer>
  </System>
  <EventData>
    <Data>1239641554979939773</Data>
    <Data>5</Data>
    <Data>RADAR_PRE_LEAK_64</Data>
    <Data>不可用</Data>
    <Data>0</Data>
    <Data>opencode-cli.exe</Data>
    <Data>1.3.11.0</Data>
    <Data>10.0.19045.2.0.0</Data>
    <Data>\?\C:\Users\nill\AppData\Local\Temp\RDR2FEA.tmp\empty.txt</Data>
    <Data>5c29ac1b-bdb5-49da-89e7-cbe85b723166</Data>
    <Data>268435456</Data>
    <Data>80d7d726d7fbb08ad134176d256465bd</Data>
  </EventData>
</Event>

3其他日志
oh-my-opencode插件日志

日志位置: C:\Users\nill\AppData\Local\Temp\oh-my-opencode.log

3.1 文件权限错误 (高频重复)

大量重复的 EPERM 错误，发生在每次启动时：

[2026-04-21T02:44:20.081Z] [migrateLegacyConfigFile] Failed to migrate legacy config file
  {"legacyPath":"C:\\Users\\nill\\.config\\opencode\\oh-my-opencode.json",
   "error":{"code":"EPERM","fd":3,"syscall":"fsync","errno":-1}}

[2026-04-21T02:44:20.086Z] [posthog-activity-state] Failed to write activity state
  {"error":"Error: EPERM: operation not permitted, fsync",
   "stateFilePath":"C:\\Users\\nill\\.local\\share\\oh-my-opencode\\posthog-activity.json"}

3.2 工具元数据恢复失败 (当前会话)

当前活跃会话中持续出现：

[2026-04-21T06:51:36.161Z] [tool-execute-after] Unable to recover stored metadata 
  and no native session linkage was present
  {"tool":"skill","sessionID":"ses_2513126bcffeot6udSgc7SJr6E",...}

[2026-04-21T06:51:55.058Z] [tool-pair-validator] Repaired missing tool_result blocks
  {"assistantMessageID":"msg_daeceda09001AH2Mhj7AFVUTeP",
   "syntheticUserMessageInserted":true,...}

会不会因此而累积内存？

3.3 子代理轮询超时 (历史)

[2026-04-14T04:00:03.757Z] [task] Poll timeout reached
  {"sessionID":"ses_275f60755ffeUAESeugvsVL17o","pollCount":1770}
[2026-04-14T04:00:03.757Z] [task] Aborting sync session
  {"sessionID":"ses_275f60755ffeUAESeugvsVL17o","reason":"poll_timeout"}

会不会因为超时后会话可能没有正确清理资源？

3.4 调用模型的问题
下面这个错误不知道哪里来的，我用的kimi coding plan。

[fuzzyMatchModel] WARNING: no match found {"target":"claude-opus-4-6","availableCount":46}
[fuzzyMatchModel] WARNING: no match found {"target":"gpt-5.4","availableCount":46}

4. windows日志中发生错误时间线

时间	事件	来源
2026-04-14 04:00	子代理轮询超时，会话中止	应用日志
2026-04-15 12:43	Windows RADAR 内存泄漏检测	系统事件
2026-04-17 02:37	Atlas session.error 事件	应用日志
2026-04-20 11:38	插件加载失败 (0 plugins loaded)	应用日志
2026-04-21 02:44	EPERM 错误爆发	应用日志
2026-04-21 06:49	当前会话启动，工具元数据恢复失败循环开始	应用日志

---

Plugins

oh-my-opencode

OpenCode version

opencode desktop v1.14.21

Steps to reproduce

just keep opencode opened for several hours

Screenshot and/or share link

No response

Operating System

windows 10 专业版 22H2

Terminal

No response

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The description appears to be an AI-generated analysis report rather than a human-written bug report. Long, AI-generated walls of text are not acceptable in issue reports.
• Please replace the description with a concise, human-written summary of the problem: what you observe, when it happens, and what environment you're using. You've already provided the key details (opencode desktop on Windows 10, crashes/disconnects every few hours) — a short description with the relevant log snippets is sufficient.

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:

• Memory Megathread #20695: Memory Megathread — tracks memory-related issues and leaks across versions
• [Bug] Desktop sidecar crashes with Bun panic "integer does not fit in destination type" after ~60s, RSS 22-25GB #23443: Desktop sidecar crashes with high RSS memory (22–25GB) after ~60s — similar pattern of memory growth leading to crash on desktop

If you believe this was flagged incorrectly, please let a maintainer know.