bug: Pi Orca Worker 初始任务被消费后无产出,并触发 cancelled-before-dispatch
- Dominant language
- TypeScript
- Stars
- 2.7k
- Forks
- 395
- Avg merge
- 21h 48m
- Merged PRs (30d)
- 776
Description
## 问题描述 / What happened
在 Codex Lead 会话中开启协同后,批量创建两个 Pi Worker:developer 带初始任务、reviewer 不带任务。developer 的初始任务回执显示已排队/派发,但随后没有任何真实产出:
- 右侧协同面板未显示 developer 的任务结果;
- developer 应创建的目标文档未出现;
- 团队仍为 active,两个 Worker 均为 `idle`;
- developer 的输入队列为空,读取到的最新 Worker 结果为空字符串;
- Lead 会话显示以下错误:
```text
cancelled-before-dispatch: Session send was cancelled before vendor dispatch: SEND//send
```
预期行为:developer 的初始任务应执行并在右侧面板显示结果;Worker 结果回传给 Lead 时不应被本地派发层取消,reviewer 随后能够审查该产物。
实际行为:初始任务似乎已被队列消费,但没有执行结果或文件产出;同时 Lead 收到 `cancelled-before-dispatch`。
## 环境 / Environment
- Cindy 版本或 commit / version or commit: 当前会话未暴露,待补充
- 平台与版本 / platform & OS version: Windows(具体版本待补充)
- 安装方式 / install method: 待补充
- Lead agent: Codex
- Worker agent: Pi(运行时解析模型为 `claude-sonnet-4-6`)
## 复现步骤 / Steps to reproduce
1. 在 Codex Lead 会话开启协同团队。
2. 使用批量创建接口创建两个 Pi Worker:
- `developer`:携带一个需要创建文档的初始任务。
- `reviewer`:不携带初始任务,等待 developer 产物。
3. 初始任务的创建回执显示任务已入队(`wakeKind: queued`)。
4. 等待 Worker 处理后检查右侧协同面板、团队状态、developer 队列与目标文档。
5. 观察到两个 Worker 均为 `idle`,developer 队列为空且结果为空、目标文档不存在;Lead 会话同时显示上述 `cancelled-before-dispatch` 错误。
## 日志与截图 / Logs & screenshots
已脱敏错误:
```text
cancelled-before-dispatch: Session send was cancelled before vendor dispatch: SEND//send
```
诊断快照:团队仍为 active;developer/reviewer 均为 `idle`;developer 队列为空;developer captured result 为空;目标文档不存在。
Contributor guide
Research direction
Start by reproducing the batch-created Pi workers with a developer task and a taskless reviewer, then trace the queued wake, worker result capture, and lead-session send path described in the report. Done means the developer produces the requested document and visible result, the lead receives it without cancelled-before-dispatch, and the reviewer can inspect the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai-infra-agents
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100