## Product Feedback Summary

オープン
#4,047 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github
領域
ai, desktop

調査の方向性

Start by reproducing the identical delegated task calls described for GitHub Copilot App 1.1.22 on Windows, comparing the refusal, verified result, and fabricated result. Review the custom-agent tool configuration and the shipped human-pasted-output mitigation. Done means real and fabricated tool results can be distinguished through verifiable provenance or an equivalent user-visible trust signal.

索引モデルが issue の本文から書いたものです。

説明

Product Feedback Summary

Issue: Custom agents in the GitHub Copilot App can non-deterministically fabricate entire tool-call results, not just prose — and this can't be reliably prevented with prompt instructions alone.

What happened: A controller agent needed to fetch a real GitHub issue. It has no direct shell tool, so it delegated to a task subagent. Across identical prompts, that subagent: refused (claimed no bash access), then succeeded once (real data, verified), then later claimed success again and returned a fully-formed, plausible JSON blob describing rich issue content — which was completely fabricated (the real issue was empty).

Why it matters: We added explicit "don't fabricate" and "quote raw tool output as evidence" instructions. Both failed, because the subagent fabricated the evidence itself. This shows prompt-level anti-hallucination guardrails have a ceiling — they can't stop a model from inventing structured "proof" of a tool call that never happened.

Root cause: Declared tool capabilities (tools: frontmatter) didn't match actual runtime access — the controller never had real bash; only a subagent could reach it, and that subagent was inconsistent about its own tool availability across identical invocations.

Ask: Expose verifiable tool-call provenance (e.g., an ID/timestamp/platform-verified marker) so agents and users can distinguish a real tool result from a fabricated one — this can't be solved by better prompting alone.

Our mitigation (shipped in the plugin): Made human-pasted CLI output the default, trusted fetch path, and require explicit human confirmation before treating any subagent-fetched data as ground truth.


Field Value
App version 1.1.22
OS Windows 10.0.26200
Theme GitHub
Path /chat
Tenure Week 19
主要言語
言語のデータがありません
スター
2.1k
フォーク
157
PR マージ指標
30日以内にマージされた PR はありません

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/app のほかの issue

github/app の issue をすべて見る

似ている issue

AI Infra & Agents の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。