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

Activity

1. github-actions commented on Oct 12, 2026

   

   github-actionsbot

   on Oct 12, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for the report. I looked at the Node SDK's send/sendAndWait path (nodejs/src/session.ts) and the MessageOptions type (nodejs/src/types.ts).

   Findings

   • The SDK forwards attachments, including type: "selection", to the runtime unchanged. I found no SDK code that drops or filters them.
   • Delivery depends on mode. The default is "enqueue", so a message sent during a running turn is queued and handled after the current turn. "immediate" interjects into the in-progress turn.
   • Once the message is accepted, the runtime decides whether and when an attachment reaches the model. This repo does not contain that code.
   • The issue body has no repro, SDK language or version, or sample call, so I couldn't reproduce this.

   Next steps

   • If you want the selection to affect the running turn, send with mode: "immediate". Check that filePath, displayName, selection and text are populated.
   • If it still doesn't reach the model, please share:
     • the SDK and CLI versions
     • a minimal send call
     • the user.message event payload, to show whether the attachments are present

   With that, we can tell whether this is an SDK or a runtime bug. I'm labeling this question until then. We can re-triage as bug once there is a repro.

   Generated by Bug Handler for #2840 · copilot · auto · 15.8 AIC · ⌖ 0.473 AIC · ⊞ 7.5K · ◷
2. github-actions

   added

   questionFurther information is requestedFurther information is requested

   on Oct 12, 2026