Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

/rubber-duck fails with GPT-6 Astra: no complementary model available (Windows, app 1.1.20)

已关闭
#3,842 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
领域
ai, desktop

调研方向

在 GitHub Copilot 应用中使用 GPT-6 Astra 重现 /rubber-duck review,然后根据报告的错误和事件日志跟踪 rubber-duck 任务以及 /subagents 的模型选择路径。将其行为与显式指定 subagent 模型时的行为以及报告 #3791 和 #3491 进行比较;当 review 使用互补模型启动,或应用给出清晰且可操作的 preflight 错误时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Summary

/rubber-duck review fails to start in a GPT-6 Astra session. The app accepts the command, but the Rubber Duck task immediately fails because no complementary model is available for the current session model.

Environment

Field Value
GitHub Copilot app version 1.1.20 (recorded by the app in the original report)
Operating system Windows 11 Enterprise, version 25H2, OS build 26200.9445, 64-bit
Session model GPT-6 Astra (gpt-6-astra), confirmed in the failed task event
Affected workflow Review in an existing local project session
Failure observed September 14, 2026, 10:41:35 UTC+08:00

Steps to reproduce

  1. Open an existing local project session in the GitHub Copilot app.
  2. Select GPT-6 Astra as the session model.
  3. After working on changes, invoke /rubber-duck review without specifying an explicit subagent model.
  4. Observe the Rubber Duck task fail immediately instead of starting a review.

Expected behavior

Rubber Duck should start an independent review using an available complementary model.

If the current session/model configuration is unsupported, the app should indicate this before starting the task and provide an actionable model-selection path, rather than accepting the command and failing immediately.

Actual behavior

  • The Rubber Duck task displays a failure indicator and "Worked for less than a second."
  • The session event log records a failed task invocation with agent_type: "rubber-duck". The start and failure timestamps are approximately 60 ms apart.
  • The runtime reports:
The "rubber-duck" subagent uses a complementary model (a different model family than your session), but none is available for your current session model. Pick a specific model for it in /subagents, or switch your session model.
  • The assistant asks the user to select a model. In the captured run, the user was unavailable, so it continued with separate General Purpose and Code Review agents and explicitly stated that this was not a cross-model Rubber Duck review.

Screenshot evidence

The reporter's screenshot shows the failed Rubber Duck task and a model-selection question. English translation of the displayed question:

Rubber-duck review could not start: the current model has no complementary model available for automatic selection. Which model should be specified for this independent review?

The screenshot has been cropped locally to exclude unrelated project information. The image attachment is pending.

Diagnostic log excerpt

The following is a minimal, sanitized excerpt from the affected session's event log, not a /collect-debug-logs archive. Private review prompts, local paths, and session/call identifiers have been omitted.

2026-09-14T02:41:35.514Z tool.execution_start
  toolName: task
  arguments.agent_type: rubber-duck
  arguments.mode: sync

2026-09-14T02:41:35.574Z tool.execution_complete
  model: gpt-6-astra
  success: false
  error.code: failure
  error.message: [exact message quoted above]

A /collect-debug-logs archive has not been collected or attached for this update.

Additional context

The log confirms the failed model selection, but does not establish why no complementary model was available. I have not verified whether explicitly selecting a model in /subagents or changing the session model resolves the problem.

Potentially related reports: #3791 and #3491. This report adds a Windows 1.1.20 occurrence with the exact runtime error.

主要语言
没有语言数据
星标
2.2k
派生
174
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/app 的其他 Issue

查看 github/app 的全部 Issue

相似的 Issue

更多 AI Infra & Agents Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。