Shadow failure case

Attachments are silently ignored when using the /fleet command

Artifact attachments-are-silently-ignored-when-using-the-flee-62e59e5bd0 · generated 2026-08-21T21:30:26.969161+00:00 · source: github/copilot-sdk #2349

This is the automatic first artifact from a falsification-bounty submission. It is redacted and public-safe by default; the next step is to turn the failure into a reusable proof, guardrail, or diagnosis.

Request private audit Follow the failure feed

Observed agent action

The /fleet command dispatches the typed message text to the agent while dropping any attached images, files, folder references, or pasted content without notice.

Expected boundary

Any message payload crossing into a command handler must preserve attachments or explicitly reject the send with a visible warning before the run starts.

Runtime context

VS Code Copilot agent session using the /fleet slash command alongside message attachments (images, files, folder references, pasted content).

Evidence supplied

The issue reports attachments are silently discarded and Fleet proceeds using only typed prompt text, with no warning, error, or other signal that context was dropped, while normal non-/fleet messages deliver attachments as expected.

Evidence needed next

No obvious evidence gaps in the first submission.

Commercial routing

Use the public artifact for broadly useful redacted failures; use the private audit path when the evidence is sensitive or the operator needs a concrete fix, guardrail, or receipt proof.

Next proof step

Convert the submitted failure into the smallest reusable control: a deterministic guardrail, receipt proof, public autopsy entry, or private diagnosis if evidence is sensitive.