makecindy / makecindy/cindy

[Desktop][Codex Subagent] 原生 Sol 路径调用 /responses 返回 502 non_sse_stream_response

Open
#4,049 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
2.7k
Forks
401
Avg merge
21h 48m
Merged PRs (30d)
776

Description

## 问题描述

Cindy Desktop v0.1.74 中,使用 Codex 供应商的 gpt-5.6-sol,关闭“Codex 智能调配”后创建 Subagent。主对话正常,但 Subagent 稳定失败。

## 复现步骤

1. 选择 OpenAI 供应商的 gpt-5.6-sol。
2. 关闭“Codex 智能调配”。
3. 新建 OpenAI 供应商 对话,发送:请只回复:模型连通成功。
4. 再发送:请创建一个子代理,让它检查当前工作目录中是否存在 README 文件;主任务最后只回复检查结果。
5. 观察 Subagent 卡片。

## 实际结果

/root/check_readme 创建后失败,自动重试 /root/check_readme_retry 后仍失败。两次均返回:

```text
502 Bad Gateway: upstream returned an invalid success response to a streaming request (non_sse_stream_response)
url: http://127.0.0.1:58436/responses
```

主 Agent 随后自行执行 PowerShell 检查并完成任务;失败卡片展开为空,没有展示错误详情。该问题已重复复现。

## 预期结果

原生 Sol/Terra Subagent 应正常完成;上游返回非 SSE 错误时,失败卡片应展示脱敏错误原因。

## 证据

Session:b01ce35c-226a-4e83-a275-7584dc3c6b11。失败集中在 Subagent 经本地 Proxy 的 /responses 流式响应链路;主对话请求和本地 PowerShell 均正常。

Image

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported Codex Subagent flow and tracing the local Proxy /responses streaming path, comparing it with the working main conversation path. Then inspect the Subagent failure-card handling. Done means native Sol/Terra Subagents complete successfully and non-SSE upstream failures show a redacted error reason.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
api, backend-api-design, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.