I'm sorry, I couldn't complete that request

[ZORfree]

Pre-submit Checks

• I have searched Zap issues and there are no duplicates.
• This bug is in Zap itself — not in upstream Zap's cloud account, billing, Warpify SSO, or cloud-only features.
• I have included relevant logs (RUST_LOG=info output, panic traces, etc.). Optional, but greatly speeds up triage.
• If the bug is in the AI / BYOP path, I have included the provider name, base URL pattern (redacted), and model id.

Describe the bug

我想在openwarp中读取我的node中，安装了哪些库，然后挑选一些没有用的库给卸载调，但是进行第一步之后某些命令执行失败还是怎么回事，后续都无法进行对话了，如下图

To reproduce

none

Expected behavior

No response

Screenshots, videos, and logs

Operating system (OS)

Windows

Operating system and version

Windows 10 22H2

Shell version

No response

Zap version / commit

v2026.05.20.preview

AI / BYOP path involved?

No — non-AI bug (terminal, blocks, UI, shortcuts, etc.)

BYOP provider (if applicable)

No response

Regression

No, this issue has existed throughout my use of Zap.

Last known good build / date (if regression)

No response

Additional context

No response

Does this block your daily use of Zap?

No

Reproducible only in Zap?

Only in Zap.

[zerx-lab]

可以提供下日志么，或者错误信息复制出来。

[ZORfree]

可以提供下日志么，或者错误信息复制出来。
程序日志吗，日志会输出在哪里呀

[hemo94931]

这个问题应该我提过pr修复，不过修的有问题，然后 @zerx-lab 又补充了新的提交
fix(ai): cancel_execution 关闭 50ms 窗口期 sender 泄漏并删除不可靠兜底 (https://github.com/zerx-lab/zap/pull/140[)](https://github.com/zerx-lab/zap/commit/d2bb4618562c37e7146e22d8ed6c564150716848)

[thful]

这个问题我这边也高频出现，至少5月22日之前高频出现，感觉像是上下文很长的时候，就会这样子

[ZORfree]

可以提供下日志么，或者错误信息复制出来。

I'm sorry, I couldn't complete that request.

Can't continue this conversation: an earlier tool result is missing or corrupted in this conversation's history, so OpenWarp can't safely send the request to your provider. Start a new conversation or fork from an earlier point to continue.

发送反馈 Debug information: {"conversation_id":""}

[lockieluke]

is there a workaround this is getting really annoying, it just happens randomly. /rewind sometimes works but not always.

[zerx-lab]

Currently, I am working on implementing a harness independent of zap, which will allow for a complete open-source release without relying on the warp open-source protocol. I will take a look at this bug when I have time, but my focus will be on the development of the new harness.

[wuchengzu]

The same problem occurs every day.

[zerx-lab]

已修复,与 #222 同一根因(commit 0d55fb9)。

打断进行中的工具调用会留下缺失 tool_result 的孤立缺口,导致 readiness 校验永久阻断对话。现已改为对这种缺口自动合成"已取消"占位结果落地历史,使会话自愈可继续。

将随下个发布版本生效。