Source selections attached while a Copilot SDK agent is running don’t reach the model

Ouverte
  • Quelque chose ne va pas ?
#2,838 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
ai-infra-agents

Piste de recherche

Start with the reproduction: create an SDK session with a pausable tool, send a steering message with mode "immediate" carrying a selection attachment, and inspect the next model request. The selection is persisted in the user.message event but is missing from that request, while the same attachment sent while idle arrives. Find where immediate-mode messages are built for the model and make them handle selections as the idle path does. Done means a regression test that sends a selection during a tool call and asserts the model request includes its text, path and range.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

I ran into this while dogfooding a language-model provider for Vercel AI Gateway I'm working on, using a Copilot chat.

While the agent was working, I attached a few source selections and asked whether some verbose validation code would benefit from Zod or another approach. The selections appeared as attachment chips in my message, but the agent asked which file I meant. When I pointed out that the selections were attached, it said it had received only a browser-page attachment.

Image

That was confusing: from my perspective, I’d already supplied exactly the context it was asking for.

What we found

I worked with an agent to trace the selections through the installed VS Code agent host. It forwards their text, file paths and ranges to the SDK, and the SDK persists them in its user.message event. However, they’re absent from the request that reaches our model provider.

We then reproduced the behavior using the installed SDK/runtime directly, with synthetic model responses and no VS Code or Vercel provider involved:

Same selection and text-blob attachments Selection reaches model Text blob reaches model
Message sent while idle Yes Yes
mode: "immediate" during a tool call No Yes

Both cases persist the attachments correctly. The comparison reproduced twice.

Reproduction
  1. Create an SDK session with a tool whose handler can be paused.
  2. Have a synthetic model response invoke that tool.
  3. While its handler is paused, send an immediate message containing a selection attachment with text, file path and range, plus a text-blob attachment as a control.
  4. Release the tool and inspect the next model request.

The steering message and text blob are present, but the selection is missing. Sending those same attachments while idle includes the selected code and its location.

Tested with the versions bundled in my VS Code installation:

  • SDK: 1.0.17-unstable.37397886721.gad270aa
  • Runtime: 1.0.92-4.unstable.r37397886721.gad270aa
Expected behavior

I’d expect source selections attached to a steering message to reach the model just as they do when sent while idle.

Reviewing code while an agent continues working feels like a pretty normal use of steering. Ideally, selection rendering would follow the same path for both delivery modes, with a regression test covering attachments sent during a tool call. The visible attachment chips should accurately represent the context the agent receives.

Langage dominant
Java
Étoiles
10.7k
Forks
1.5k
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/copilot-sdk

Toutes les issues de github/copilot-sdk

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.