ai-harness: a forwarded command completes with no result, also when the owner rejects it
维护者通常 1 天内回复
@tombeckenham 已经在做这个了。
开始于 2026年10月15日。
评估
这个 Issue 还没有评估数据。
描述
TanStack AI version
@tanstack/ai-harness on the feat/harness-core branch, with #1780 (not released yet).
Framework/Library version
Node 24.8.0. No UI framework: the bug is in the durable host.
Describe the bug and the steps to reproduce it
With #1780, a durable host passes an input for a thread that another host owns to stores.inbox, and the owner runs it. For session.command(...), the host that passed it on ends the command operation right away with status completed and the result undefined.
So the caller gets a wrong answer in two cases:
- The command returns a value: the caller gets
undefined. - The owner rejects the command (
unknown_command, invalid input) or the command throws: the caller still getscompleted.
The real result exists only in the owner's events. Code: executeCommand in packages/ai-harness/src/session/turn.ts.
Steps:
- Open one thread on two durable hosts that share
log,runs,workClaims, andinbox. - Start a turn on host A, so A owns the thread.
- Call
hostB.command('unknown')while the turn runs. - The operation on host B completes with
undefined. On host A, the command is rejected.
Possible fixes:
- Host B waits for the owner's result in the log (a settled record for the command input), and ends its operation with it.
- Host B ends the operation with a receipt only (
queued), and the docs say that a forwarded command has no result.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
packages/ai-harness/tests/forwarding.test.ts on #1780 has the two-host setup (sharedStores()). Use it with the steps above, and expect the operation on host B to fail.
Do you intend to try to help solve this bug with your own PR?
Maybe, I'll investigate and start debugging
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
- 主要语言
- TypeScript
- 星标
- 3.2k
- 派生
- 372
- 平均合并
- 1 天 16 小时
- 30 天内合并 PR
- 244
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TanStack/ai 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
维护者通常 1 天内回复
-
Durable resume through withPersistence never fills ctx.inputResponse for mcp_input interrupts可能已有人在做 @tombeckenham 于 3 天前认领。 未关闭waiting-on: maintainer
维护者通常 1 天内回复
-
ai, ai-persistence: a nested subagent that waits runs again from the start under withPersistence可能已有人在做 @tombeckenham 于 4 天前认领。 未关闭waiting-on: maintainer
维护者通常 1 天内回复
-
ai-ollama: streamed chat() reports finishReason "stop" when done_reason is "length"可能已有人在做 @AlemTuzlak 于 4 天前认领。 未关闭waiting-on: maintainer
维护者通常 1 天内回复
-
Discriminate status-dependent record and option types (RunRecord, SessionIndexEntry, InputState, durable-only options)可能已有人在做 @jherr 于 10 天前认领。 未关闭enhancement waiting-on: maintainer
维护者通常 1 天内回复
相似的 Issue
-
Native Web
难度 1/5 1 小时以内 新手友好度 80/100
digitalfabrik/integreat-app#4517 ·
维护者通常 2 天内回复
-
TLS guide repeats certs/ in the certificate directory可能已有人在做 @maheshrijal 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
prometheus/docs#3156 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
medusajs/dtc-starter#90 ·
维护者通常 1 天内回复
-
usability
难度 2/5 1-3 小时 新手友好度 72/100
inmanta/web-console#7632 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
zaidmukaddam/scira#261 ·