You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 19, 2026
🔗 Related PRs
#595 - 修复:上游错误统一按候选失败顺延 [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
sixsixdog commentedon Nov 20, 2026
补充:根因已定位到插件侧。
同一上游模型走另一个实现(workbuddy2api-hub)时 512 / 600 条消息都是 200,说明不是上游限制;而 Agent2API 侧 512 条消息的请求,插件计量显示
durationMs=18、hostCalls=16,没有发出上游请求就直接失败了,对外被映射成bad_params+ 文案「WorkBuddy网络请求未完成」。所以这条 issue 的核心诉求不变、而且更重要:插件在本地就能判定的错误不应被归类成不可重试的
bad_request,且文案必须透出真实原因(消息数超限),否则客户端只能看到「网络问题」并反复重试。细节与对照数据见 ProvidersPlugin/Agent2Providers#48 的最新评论。
sixsixdog commentedon Nov 20, 2026
补充一条更关键的数据点:内置 provider(CodeArts)同样在 513 条消息处失败。
msgs=512msgs=513msgs=547msgs=2但 body 1.9 MB说明这个上限不是某个插件 provider 私有,而是宿主侧共用的对话预处理/转发层里的 512 条消息上限;不同 provider 只是把它包装成不同错误文案,然后统一落进
bad_request → return_error(不可重试、整轮失败)。因此本 issue 的两条诉求更强了:
too_many_messages+ 当前条数/上限),不能伪装成上游网络错误 —— 现在面板上看到的是「上游未完成本次请求」「网络请求未完成」,完全误导排查方向。