GitHub Release Notes

Attach images and videos to issues and pull requests

The repeatable --attach flag uploads local images and videos and adds them to issue, pull request, or comment bodies. If a body already references the local path, gh replaces it with the uploaded URL; otherwise it appends the attachment:

# Attach files when creating or editing an issue
gh issue create --attach './repro.png#The error state'
gh issue edit 123 --attach ./walkthrough.mp4

# Attach files when creating or editing a pull request
gh pr create --attach ./before.png
gh pr edit 456 --attach ./after.png

# Attach files to comments
gh issue comment 123 --attach ./repro.png
gh pr comment 456 --attach ./result.mp4

Repeat the flag to attach multiple files in a single invocation. Attachments are available on GitHub.com and GitHub Enterprise Cloud.

For more information see https://gh.io/gh-attach and https://github.blog/changelog/2026-09-01-github-cli-media-in-issues-pull-requests-and-comments/

Worktree support extended to gh issue develop

gh issue develop can now create a linked branch and check it out in a new Git worktree, leaving your current working copy unchanged:

# Create a linked branch for an issue and check it out in a worktree
gh issue develop 123 --checkout --worktree /path/to/wt-feature

What's Changed

✨ Features

Add token and repository metadata required for attachment uploads by @BagToad in #14177

Add validation for attachable image and video files by @BagToad in #14178

Rewrite local Markdown references to uploaded attachment URLs by @BagToad in #14179

Add attachment uploads to GitHub by @BagToad in #14180

Add repeatable --attach flag parsing and upload orchestration by @BagToad in #14181

Add --attach to gh pr comment and gh issue comment by @BagToad in #14182

Add --attach to gh pr create and gh pr edit by @BagToad in #14183

Add --attach to gh issue create and gh issue edit by @BagToad in #14184

Add worktree checkout to gh issue develop by @sergiou87 in #14136

Use text-only spinner output when gh is invoked by a coding agent by @niik in #14191

Honor PI_CODING_AGENT_DIR for Pi user skills by @tommaso-moro in #14260

🐛 Fixes

fix(repo sync): explain when the target branch is checked out in another worktree by @williammartin in #14076

fix(pr merge): safely handle --delete-branch with linked worktrees by @tidy-dev in #14007

fix(copilot): end the declined-install warning with a newline by @BagToad in #14222

fix(attach): clarify retry windows and attachment path resolution by @BagToad in #14262

fix(issue develop): reject non-empty worktree targets before creating a branch by @tidy-dev in #14244

fix(repo sync): prevent linked-worktree corruption by @sergiou87 in #14060

fix(view): reject --comments with --json by @BagToad in #14215

fix(attach): limit batches to 50 files by @BagToad in #14289

fix(skills): install Codex user skills to ~/.agents/skills by @scarletkc in #14154

📚 Docs & Chores

Address review feedback across the --attach stack by @BagToad in #14200

Refactor commands to own attachment flag policy by @BagToad in #14255

Document attachment support in the gh skill by @BagToad in #14261

Document gh issue develop --checkout --worktree in the gh skill by @babakks in #14265

Clarify pull request testing guidance by @williammartin in #14272

Fix issue triage to apply suspected-spam labels directly by @williammartin in #14271

Prevent Dependabot from updating agentic-workflow dependencies by @williammartin in #14274

Modernize Go code with go fix by @BagToad in #14278

Dependencies

chore(deps): bump google.golang.org/grpc from 1.83.0 to 1.83.1 by @dependabot in #14247

chore(deps): bump charm.land/bubbletea/v2 from 2.0.8 to 2.0.9 by @dependabot in #14248

chore(deps): bump the codeql-actions group across 1 directory with 3 updates by @dependabot in #14250

chore(deps): bump charm.land/bubbles/v2 from 2.1.1 to 2.2.0 by @dependabot in #14249

chore(deps): bump agentic-workflows to 0.87.5 by @williammartin in #14273

chore(deps): bump charm.land/bubbles/v2 from 2.2.0 to 2.2.1 by @dependabot in #14275

chore(deps): bump https://github.com/sigstore/protobuf-specs from 0.5.1 to 0.5.2 by @dependabot in #14258

chore(deps): bump https://github.com/google/go-containerregistry from 0.21.9 to 0.22.0 by @dependabot in #14267

chore(deps): bump google.golang.org/grpc from 1.83.1 to 1.83.2 by @dependabot in #14299

chore(deps): bump azure/login from 3.0.1 to 3.0.2 by @dependabot in #14301

chore(deps): bump the codeql-actions group with 3 updates by @dependabot in #14300

New Contributors

@scarletkc made their first contribution in #14154

Full Changelog: v2.98.0...v2.99.0

You can now set an optional expiration date on an individual user budget, and GitHub removes the budget on that date. This capability is generally available. The user then falls back to the next budget that applies to them (i.e., their cost center per-user budget or otherwise your universal budget).

Previously, you had to remove every temporary budget override by hand, creating recurring cleanup work at enterprise scale.

When you create or edit an individual user budget, you can choose:

• No expiration, which is the default and matches current behavior.
• Expiration at the start of the next billing cycle.
• Expiration on a specific date.

You can change or clear an expiration date at any time.

Set an expiration date in your billing settings, or use the expires_at field in the Budgets REST API when you create or update a budget.

Expiration dates are available for the GitHub Copilot Business and Copilot Enterprise plans.

Learn more about setting up budgets and the Budgets REST API.

The post Set an expiration date for individual user budgets appeared first on The GitHub Blog.

Copilot now tells you when a pull request is ready to approve, and admins can authorize it to sign off on approval. The ability for Copilot to approve is off by default and configurable at the enterprise, organization, and repository level. The approval assessments will now appear as a part of the overview comment in every Copilot review. This feature is available in public preview to GitHub Copilot Pro, Pro+, Max, Business, and Enterprise plans.

✅ Approval assessments

Every Copilot code review now includes an approval assessment in the overview comment. The assessment signals whether Copilot considers the pull request ready to approve, giving you an at-a-glance read on its judgment alongside its detailed comments.

An approval assessment alone does not count toward merge requirements. Copilot’s determination is surfaced so you can decide how to act on it.

⚙️ Turning on approvals

By default, Copilot will not approve pull requests. When enabled, Copilot can submit an approval that counts toward the repository’s required-approvals rule. If new commits are pushed after Copilot approves, its approval is dismissed just like a human reviewer’s, and you can request a new review from Copilot to get a fresh approval.

Admins control this behavior at three levels:

• Enterprise: Admins can leave approvals off for the whole enterprise or let organizations decide.
• Organization: Admins can turn approvals on org-wide, let repository admins decide, enable it for specific repositories, or turn it off org-wide.
• Repository: Admins can turn approvals on or off, and choose which file paths Copilot is allowed to approve.

To learn more about configuring approvals for your enterprise, organization, or repository, see the Copilot code review documentation.

The post Copilot code review can now approve pull requests appeared first on The GitHub Blog.

You can now block or unblock users directly from discussion comments in repositories owned by personal GitHub accounts, extending the in-context blocking controls already available for issue and pull request comments.

To block or unblock a user from a discussion comment:

• Open the More menu on their comment.
• Select Block user or Unblock user.
• Optionally add a private note explaining why you’re blocking the user.
• Confirm your selection.

If you have any questions or feedback, join the discussion in our community discussion.

The post Block users from discussion comments in personal repositories appeared first on The GitHub Blog.

GitHub CLI now has a repeatable --attach flag that uploads a local image or video and references it inline in an issue, pull request, or comment body.

This is now generally available to all users on GitHub across all plans. You just need to update gh to v2.99.0.

Why this matters?

Some things are easier to show than to describe (i.e., a UI bug, a rendered result, an error on screen). Previously, gh only wrote text, so adding an image or video to an issue or pull request meant stopping to open the browser, drag the file into the comment box, and copy the result back. Now, gh can attach images and videos directly from the command line.

--attach puts the image in the same command that writes Markdown. File the bug, and the screenshot lands with it, so the issue shows the actual problem the first time. Open the pull request with a before and after, and the reviewer sees the change instead of pulling the branch to check. Your coding agents get this too, so they can show a result rather than describe it.

Capabilities

Attach from commands that write Markdown text: --attach is repeatable and works on gh issue create, gh issue edit, gh issue comment, gh pr create, gh pr edit, and gh pr comment.

Keep your Markdown as written: A local path already referenced in the body is rewritten in place, so keeps its alt text and becomes the uploaded asset. Anything attached but never referenced is appended at the end.

Post images and video: PNG, JPEG, GIF, WebP, SVG, MP4, MOV, and WebM are all supported.

Describe what you attach: Alt text follows the path after #, as in --attach './login.png#The login error state'. Omit it and gh falls back to the filename.

Security and access controls

Uploads authenticate with the common token types gh already uses, either the OAuth token from gh auth login or a classic personal access token. Write access to the repository you are attaching to is required for image uploading.

--attach is generally available to all users on GitHub across all plans, with no preview period. Size limits match the web upload flow: 10 MB for images and GIFs, 10 MB for video on Free plans, and 100 MB for video on paid plans. GitHub Enterprise Server is not supported in this release.

Getting started

Update gh to v2.99.0, then run gh issue comment --attach ./screenshot.png. --attach works the same way on gh issue and gh pr create, edit, and comment. Run gh help for the full flag reference.

Join the discussion on the GitHub Community and read the docs to learn more about attaching files from the command line.

The post GitHub CLI: Media in issues, pull requests, and comments appeared first on The GitHub Blog.

Added

• Add Recent, Created, Name, and classic None sorting to the split Sessions sidebar, with the selected order saved across restarts
• Enterprise admins can pin sign-in to approved GitHub organizations with the forceLoginOrgs managed setting

Improved

• /mcp config and the MCP add/edit/authenticate forms now open in the plugins dashboard instead of a separate MCP manager, so closing a form returns to the server list.
• File path autocomplete stays fast in large repositories
• Plugin list commands and /plugin now show bundled built-in plugins.
• Improve sandboxed Bazel and Bazelisk runs by granting required cache and output paths; macOS requires a future Bazel release or additional sandbox capabilities
• The collapsed autopilot goal panel now reads as a single-line pinned prompt, keeping the frame it shares with a pinned prompt instead of compressing into a bare band wedged against the chrome above it

Fixed

• A relative --add-dir or --plugin-dir path now resolves against the session's working directory under --resume=<id> and --worktree, instead of the directory the CLI was launched from. Relative values are also resolved after -C is applied, so -C no longer has to precede either option on the command line
• MCP servers contributed by a plugin are no longer labelled "User" in the MCP dashboard, and a server from a bundled plugin is now shown as built-in and names the plugin it came from.

We have updated how model access is determined for Copilot users who hold seats in more than one organization. To keep billing and governance in sync, your model access is now determined only by the organization paying for your usage.

What’s changing

Before this change, if you had Copilot seats in more than one organization, you could use a model as long as any of your organizations enabled it. With this update, your billing organization decides model access. You can find this organization under “Usage billed to” in the Copilot features page. For more information about how policies apply, read the GitHub Copilot policy documentation.

What isn’t changing

If your Copilot access comes entirely through an enterprise or its organizations, your model access will not be impacted by this update.

The post Copilot model access update for GitHub Team plans appeared first on The GitHub Blog.

This changelog covers VS Code v1.132 through v1.135, shipped throughout August 2026.

These releases make it easier to organize agent sessions, review changes, and navigate long conversations. Agent Host, the integrated browser, and dictation also get updates to support more ways of working in VS Code.

Agent sessions and workflows

The Agents window adds more ways to organize related chats, follow agent activity, and move between prompts and their file changes.

• Arrange chats side by side: Keep multiple chats visible in horizontal or vertical groups to compare results or follow your agent’s work, with the layout restored when you return to the session.
• Open a side-conversation: Type /btw to open a side chat that shares the primary chat’s context and prompt cache while it continues running.
• Navigate the chat conversation: Use the prompt timeline control from the transcript gutter to easily navigate to specific prompts in chat and review the related file changes.
• Install portable agent plugins: Install agent customizations from plugins that follow the Agent Plugins 1.0 standard across VS Code and other compatible agent clients.
• Open the Agents window without GitHub sign-in: Enable the experimental setting to open the Agents window without GitHub sign-in when Claude is configured with an API key.
• Switch model providers in Claude sessions: Choose between models from your Anthropic subscription and Copilot subscription at any time.
• Continue external agent sessions: View and continue recent Copilot or Claude agent sessions created in other applications from the Sessions list in VS Code.
• Connect windows to the same session: Use the Agent Host to connect to the same agent session from multiple VS Code windows.
• Get a second opinion: Try the experimental /rubber-duck command in a Copilot Agent Host session to ask a complementary model to surface missed details and edge cases.
• Review session details next to chat: Use the default single-pane layout to open session details and editors in one side pane, with diffs that adapt to the available width.

See it in action in our Agent Host introduction YouTube video.

Chat and review

Chat updates make it easier to find information in long conversations and review changes in agent-generated content.

• Find text across a conversation: Avoid endless scrolling to find a search term with text search across the complete chat transcript with options for case matching, whole words, and regular expressions.
• Keep the current prompt visible: Don’t lose track of which prompt a response belongs to with chat sticky scroll, which keeps the current prompt pinned while you scroll through a long conversation.
• Review rendered Markdown diffs: Combine viewing diffs and editing Markdown in a single experience with the experimental hybrid Markdown editor.
• Switch editor types from the breadcrumb bar: Switch between regular and diff editors from the breadcrumb bar in the Agents window.
• Resize terminal output in chat: Expanded terminal output in Chat now reflows as you resize the view, making it easier to read at different widths.
• View token usage by model: Hover over the response footer to see input, cached input, and output token usage for each model in a chat turn.

Integrated browser

The integrated browser makes it easier to give agents feedback on web pages and see local HTML changes as you work.

• Comment on web page elements: Select and annotate several HTML elements on a page to provide targeted UI feedback, which the agent can then address in batch.
• Reload HTML files automatically: See saved changes and agent edits immediately as local HTML files automatically reload when they change on disk.
• Open HTML files in the browser by default: If you often preview local HTML files instead of editing them, you can now set the integrated browser as their default editor by configuring the editor associations setting.

Dictation

Built-in dictation now supports multiple languages, project-specific instructions, and shell-aware cleanup for terminal commands.

• Dictate in multiple languages: Dictate in multiple languages with an on-device model. Choose your language or let VS Code automatically detect it.
• Customize transcript cleanup: Add user-level or workspace-level instructions so dictation follows your project terminology and formatting preferences.
• Improve dictation for terminal commands: Shell-aware cleanup preserves command syntax instead of inserting spoken punctuation literally.

Browse the full release notes for VS Code 1.132, 1.133, 1.134 and 1.135 to explore everything that’s new.

Download the latest version of VS Code and, as always, happy coding!

The post GitHub Copilot in VS Code, August 2026 releases appeared first on The GitHub Blog.

Added

• Add automatic HTTPS proxy mTLS client certificate support for model and web requests
• Detect the herdr terminal multiplexer instead of mistaking it for tmux, so the Kitty keyboard protocol, color scheme following, terminal progress, /copy and notifications work in herdr panes

Improved

• Improve /sandbox policy by grouping path grants by source and showing detected developer tools

Fixed

• The newest line of output stays visible above the input box instead of hiding behind it, except while a prompt is pinned to the top of the transcript
• Exporting a resumed session with --share or --share-gist writes the whole transcript instead of only the latest run

GitHub Copilot in Slack and Microsoft Teams

This week’s updates give you more control over how Copilot runs, from team sessions in Slack and Teams to customization across the app, CLI, and your IDE.

Turn team conversations into shared agent sessions. Mention @GitHub to investigate problems, plan work, and make changes your team can follow and guide together.

GitHub Copilot app

The Customize tab is now generally available, bringing MCP servers, plugins, skills, and canvases together in one place.

Turn Azure DevOps issues and pull requests into Copilot sessions from the Customize tab.

Work in your Linux environment with experimental support for Windows Subsystem for Linux (WSL).

Split and move any tab to keep related work side by side.

Send any browser preview straight to your external browser from the tab’s context menu.

Try the Copilot app.

GitHub Copilot CLI

Start every new session with your preferred execution and permission modes using defaultMode and defaultPermissionMode.

Manage plugins, MCP servers, and skills more easily with new experiences in /plugin, /mcp, and /skills.

Pick up where you left off by restoring sessions that did not exit cleanly, including sessions interrupted mid-turn.

Get significantly faster performance now that Copilot CLI runs on a native Rust runtime, while its terminal interface remains built in TypeScript.

Install the Copilot CLI.

GitHub Copilot for JetBrains

Apply consistent enterprise controls for Copilot in JetBrains, including plugins, MCP servers, telemetry, and agent permission modes.

VS Code 1.135 release updates

Continue recent Copilot or Claude agent sessions from other applications in VS Code.

Get a second opinion from a complementary model to surface missed details and edge cases.

Stay focused on your work with a new single-pane Agents layout, simpler session controls, and session details that are easier to find.

See detailed chat usage by model for every chat turn.

Explore everything that’s new with VS Code 1.135 in the full release notes.

GitHub Copilot for Visual Studio

Pin favorite models, hide unused ones, compare capabilities and costs, and adjust reasoning effort for each task.

Share custom agents across your organization to standardize workflows and improve discovery.

View Copilot plan consumption and manage premium model usage before reaching limits.

Review uncommitted changes or individual commits with the Git agent before opening a pull request.

Install the latest version of Visual Studio with GitHub Copilot.

The post GitHub Copilot weekly releases — August 24 appeared first on The GitHub Blog.

Reopening Copilot Business and Enterprise signups with billing updates

To provide a strong, consistent Copilot experience, we’re making three separate, upcoming changes to Copilot policies and billing. Please review the upcoming updates to understand what may impact you.

Starting September 1, 2026, GitHub will start reenabling sign-ups for new Copilot Business and Copilot Enterprise customers paying by credit card or PayPal. To improve availability and reliability of Copilot services, we’re strengthening account vetting and updating billing experiences for customers who pay by credit card or PayPal.

What’s changing

All new Copilot Business or Copilot Enterprise seat assignments will require payment for each seat before users gain Copilot access.

At the start of the next billing cycle, all Copilot Business and Copilot Enterprise seats assigned will incur an upfront charge. This will apply to existing Copilot Business and Copilot Enterprise customers with a credit card or paypal payment method starting October 1, 2026.

If you exceed your included usage, additional payment may be required for you and your users to continue using Copilot.

Included usage may be prorated across the month to align with the seat cost proration.

What’s not changing

Copilot Business and Copilot Enterprise prices are not changing.

Revoking a seat does not result in a prorated refund. The removal will be reflected in your next monthly billing cycle.

All seats added in the middle of a billing cycle will continue to be prorated from date of assignment to end of bill cycle.

Additional usage exceeding included allowances will remain available for purchase.

Spend controls, usage tracking, and the option to purchase additional AI credits will remain available.

Existing Copilot Business and Copilot Enterprise customers can expect these billing updates to take effect starting October 1, 2026.

Fully canceling Copilot and returning later may trigger updated account vetting and billing behaviors.

For more information, read our Copilot Quick Start documentation.

Copilot cloud agent, Copilot Chat on github.com, and Copilot Chat in GitHub Mobile are converging to a single experience and policy

No earlier than September 28th, 2026, GitHub will relaunch Copilot Chat on github.com, Copilot Chat in GitHub Mobile, and GitHub Copilot cloud agent as a single, unified Copilot experience.

What’s changing

The separate policies for these experiences will be replaced by a single policy.

This unified Copilot experience will be enabled by default after launch.

Cloud agent will leverage Sandbox to provide a faster cloud experience.

Copilot on github.com will fully migrate to the agent sessions experience, previously used only by Copilot cloud agent. As a result, chat data will be retained for the life of the account instead of 28 days, aligning with our existing Copilot cloud agent experience.

Stay opted in

No changes are required to keep Copilot available on github.com and GitHub Mobile. However, if you opt out of the unified experience, you or your teams will lose access to Copilot on github.com and GitHub Mobile after the new experience launches.

Business and enterprise administrators should review the policy before September 28th, 2026 and confirm that it reflects how they want to manage Copilot access for their teams.

To update the policy:

• Go to Copilot settings on github.com.
• Select Copilot cloud agent (coming soon).
• Set the policy option.

Copilot code review default is changing to Balanced effort level

Following the release of Copilot code review effort levels, the default review effort level for GitHub Copilot code review is changing from Lite to Balanced.

How review effort level defaults work

You can set a default review effort level at the organization and repository levels:

• The organization default applies to all repositories owned by the organization that haven’t selected their own review effort level.
• The repository default applies to all automatically requested reviews within the repository. For manually requested reviews, you can select which effort level is used from the “Reviewers” bar in the pull request.

Balanced is becoming the default effort level

For existing and new repositories and organizations using Copilot code review, the review effort value of Default uses Balanced starting September 28th, 2026.

If you’d prefer to keep Lite as your default experience, change your review effort level away from Default and explicitly select Lite in your repository or organization settings before September 28th, 2026. We’ll respect that selection and won’t switch your default to Balanced.

Review the Copilot code review documentation to understand how this may affect your usage.

The post Upcoming changes to GitHub Copilot policies and billing appeared first on The GitHub Blog.

Highlights

Here’s what’s new with GitHub Copilot in Visual Studio 2026. Check the Insiders channel for the latest:

• Organization-level custom agents: GitHub organization and enterprise owners can publish custom agents for use across repositories in their organization. Visual Studio automatically detects these agents and shows both their descriptions and organization source in the agent picker. This functionality requires a GitHub organization.
• Access your Copilot usage: Open the context window from the Copilot prompt box, then select View all Copilot usage to see your full plan details. Refined notifications also make it clearer when you are approaching a limit and what options are available.
• Adjust model thinking effort to match your task: Supported models now offer Low, Medium, and High thinking effort controls. Use lower effort for straightforward work or higher effort for complex debugging, algorithms, and architecture decisions. This enables you to balance reasoning depth with token usage.
• Better model control: Pin favorite models, collapse models you use less often, and select Manage models for a detailed view. The management view includes model capabilities, context window sizes, cost information, and controls for Copilot and custom models.
• Review changes and commits with the Git agent: Ask the Git agent to review uncommitted changes or commits before you open a pull request. Findings appear inline in the editor with a navigable list in Git Changes. You can continue the Copilot Chat conversation to understand or address each suggestion. Reviews work with GitHub and Azure DevOps repositories.

This update is available to users on all GitHub Copilot plans, including Copilot Free, Student, Pro, Pro+, Max, Business, and Enterprise.

To learn more about what’s new, check out the Visual Studio blog and release notes.

What’s next for Copilot in Visual Studio

Stay up to date on the latest Copilot features by following the Visual Studio blog, where you’ll find roadmap updates and opportunities to share feedback.

The post GitHub Copilot in Visual Studio — August update appeared first on The GitHub Blog.