GitHub Copilot Vision is GA: what developers can attach now

GitHub Copilot Vision is confirmed generally available as of July 1, 2026. Developers can attach images and PDFs to Copilot prompts so the assistant can reason over visual context next to code, with availability across supported Copilot plans and surfaces.

What changed

GitHub moved Copilot Vision from preview-style rollout to general availability. The GA changelog says Copilot can now accept visual files in chat prompts, including images and PDFs, so developers can ask questions about screenshots, UI mockups, diagrams, error captures, or design references without translating everything into text first.

The rollout covers GitHub Copilot Chat in VS Code, Copilot Chat on github.com, and Copilot CLI image paths. GitHub says the feature is available to Copilot Free, Pro, Pro+, Business, and Enterprise subscribers, with no new policy or admin action required to turn it on.

Why this is early

The first strong signal is GitHub's own July 1 changelog, which is the primary source for the GA status and the supported Copilot surfaces. GitHub's documentation independently confirms that Copilot workflows support image attachments, and the Copilot CLI docs also describe image and PDF attachment behavior.

This is not a leak or pre-announcement. The remaining uncertainty is operational: exact UX details can differ by client version, organization policy, model selection, and plan-level limits.

Key takeaways

• Copilot Vision is now GA, not just a preview feature.
• GitHub says all Copilot subscriber tiers can use it, including Free and Enterprise plans.
• VS Code supports attaching images in chat; github.com supports images and PDFs; CLI workflows can use image paths.
• Business and Enterprise teams should review attachment retention and internal data rules before sending customer screenshots or confidential PDFs.
• Teams using custom Copilot SDK flows should check model vision support before paying for image tokens.

Availability and access

GitHub lists the feature as generally available from July 1, 2026. For Business and Enterprise customers, GitHub says the old Editor Preview Features policy requirement is no longer needed, because Vision is now enabled by default.

GitHub also notes that Business and Enterprise image and PDF attachments are retained for about 24 hours to provide the service. That makes the feature useful for debugging and UI review, but it still needs internal rules for secrets, customer data, unreleased designs, and regulated documents.

Practical LinkLoot angle

Copilot Vision is most useful when the problem is visual but the fix is code. A developer can attach a broken layout screenshot, a Figma export, an accessibility issue capture, a chart, or a PDF spec and ask Copilot to map the visual evidence to files, tests, or implementation steps.

Use it as a context shortcut, not as a source of truth. For production changes, ask Copilot to cite the files it touched, explain assumptions, and produce a test or manual verification path. For more agent workflow ideas, keep LinkLoot's guide to AI agent tools nearby.

What to verify before you act

• Confirm your Copilot client is updated and supports the attachment surface you plan to use.
• Check whether your chosen model has vision support before attaching images in SDK or CLI workflows.
• Review organization policies for screenshots, PDFs, customer data, secrets, and unreleased product designs.
• For Business and Enterprise use, account for GitHub's stated attachment retention window.
• Treat Copilot's interpretation of diagrams and screenshots as a draft; verify against code, tests, and source files.

Source check

Confirmed by:

• GitHub Changelog: Copilot Vision is generally available, with supported surfaces and plan availability.
• GitHub Docs: Copilot CLI and Copilot SDK documentation describe image attachment workflows and vision support checks.

Context:

• The prior preview period created confusion around whether image input required special extension or preview policy access. The GA changelog is the update trigger here.