makecindy / makecindy/cindy

#2687 Auto 权限审阅器故障修复后,调用审批桥会超时(超过600秒)

Open
#2,851 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
2.7k
Forks
395
Avg merge
21h 48m
Merged PRs (30d)
776

Description

### 问题描述 / What happened

https://github.com/makecindy/cindy/issues/2687
这个问题在0.1.50版本修复后,使用 Auto 权限,仍被审批桥阻塞:连续三次写入均返回 patch rejected by user 。

AI 排查后反馈是因为审批超时所导致,怀疑过可能是网络问题,但是同时期测试网络状态无明显异常,再次重新提交审批后问题依旧。

### 环境 / Environment

- Cindy 版本或 commit / version or commit: 0.1.50
- 平台与版本 / platform & OS version: windows
- 安装方式 / install method: exe直接安装

### 复现步骤 / Steps to reproduce

已确认。本次日志更像是“审批等待超时后被映射为拒绝”,没有证据表明您主动点击了拒绝。

补丁调用 开始时间(北京时间) 结束时间 结果 等待时间
创建测试文件,首次 11:26:34 11:36:34 declined 约 600 秒
创建测试文件,重试 11:37:04 11:45:31 completed 约 507 秒
写入三态类型与实现 11:46:10 11:56:11 declined 约 600 秒
单独写入三态实现 11:56:38 12:06:38 declined 约 600 秒

关键日志:

Cindy 主日志在 11:36:34、11:56:11、12:06:38 三次记录: codex_core::tools::router: error=patch rejected by user
Codex 会话日志将失败事件记录为: status: "declined"、success: false、stderr: "patch rejected by user"
日志中没有记录拒绝操作者、点击事件或 decisionSource=user。
三次失败都精确接近 600 秒,符合审批请求十分钟未解决后超时的特征。
本次排查期间,一个只读日志查询也在约 600 秒后返回 exec command rejected by user,进一步说明不是补丁内容或文件权限导致。
日志文件:

Cindy 主日志
Codex 会话日志
相关调用 ID:

exec-1851adc8-06a2-4a31-8f73-b820c93a90ba:失败
exec-9a5f02ba-985a-450c-b081-e10aee89adef:成功
exec-21a43557-ea45-4ded-97ee-0aac3cd22a7a:失败
exec-4dc90227-aa68-4d7c-87fb-a4cf62ec186e:失败
结论:patch rejected by user 在这里是误导性的通用错误。实际问题高度疑似 Auto 审批桥没有及时返回结果,达到约 600 秒截止时间后被 Codex 记为 declined。

### 日志与截图 / Logs & screenshots

Image
Image
Image

[2026-08-16-cindy-patch-approval-timeout-report.zip](https://github.com/user-attachments/files/31127193/2026-08-16-cindy-patch-approval-timeout-report.zip)

Contributor guide

Open the contributing guide

Research direction

Start by correlating the Cindy main log, Codex session log, and attached report for the four listed call IDs, focusing on the repeated 600-second waits and approval-bridge responses. Trace the approval path from those events and reproduce the Auto-permission flow; done means an unresolved approval timeout is handled distinctly from an explicit user rejection and the repeated failure case no longer reports a misleading decline.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
ai, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.