github / github/copilot-cli

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

Open
#2,860 0 comments 0 reactions 0 assignees View on GitHub
area:agents area:tools
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

### 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_

Contributor guide

Open the contributing guide

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ai, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.