github / github/copilot-cli

CAPIError 400 when agent using `view` tool with GIF file -> blocks autopilot and essentially stops after error.

オープン
#2,860 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
area:agents area:tools
主要言語
Shell
スター
11.2k
フォーク
1.9k
平均マージ
14時間 16分
マージ済み PR(30日)
6

説明

### Describe the bug

I got a very similar issue as #2859 with CoPilot CLI reporting same. Was in `autopilot` and it tried to view a GIF image, it tried 3 times, and failed. I prompted, "you look stuck. the last tool call had an exception. please continue". I tried the same tool call again, also failing with "CAPIError" 400. If you can pull session: 8ef59e57-7242-4fa6-9939-5c6bb8aa65af that has it. But agent trying to `view` a GIF failed in my case. I do not have the full error message.

Additionally, I explained after the work was done to `copilot` in "Auto" mode (it seem to pick Haiku, which may not been ideal), that it should, "review session 8ef59e57-7242-4fa6-9939-5c6bb8aa65af and report the issue"... instead it suggested this repo's name, without any additional context on the session that might be useful here.

### Affected version

GitHub Copilot CLI 1.0.34.

### Steps to reproduce the behavior

Agent tries to view a GIF as part of autopilot, and it will stop the work. Only explicit prompting to say "You got a CAPIError". Did not repo again, as it was part of larger work to capture screenshots from a terminal using `vhs`.

### Expected behavior

`autopilot` should recover from an error, and continue it's work. A tool call failure should be handled more gracefully.

### Additional context

_No response_

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

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

調査の方向性

Start by reproducing the GIF view failure during autopilot with GitHub Copilot CLI 1.0.34, using the reported session and the terminal screenshots workflow involving vhs if available. Trace how the CAPIError 400 from the view tool is handled; done means autopilot recovers from the failed tool call and continues rather than stopping.

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

評価

技術スタック
shell
領域
ai, cli
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
静か
明瞭さ
説明が足りない
初心者へのやさしさ
35/100

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

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