Browse GitHub Copilot Blogs (11)

Emanuele Bartolesi shares a practical fix for high CPU/disk usage on Windows 11 when running Claude, Codex, and GitHub Copilot tooling: adding targeted Microsoft Defender Antivirus folder exclusions. The post also calls out the security tradeoff and walks through the exact Windows Security steps to apply exclusions safely.

Rob Bos shares a short pointer to his Azure Heroes session on how he works with GitHub Copilot, with a link to download the slides.

DevClass reports on Microsoft’s migration of the GitHub Copilot runtime from TypeScript/Node.js to Rust using AI agents, including token costs, release cadence, performance benchmarks, and the practical risks of compiler-passing regressions when LLMs generate Rust at scale.

Jesse Houwing breaks down a nasty PSScriptAnalyzer failure in GitHub Actions where Invoke-ScriptAnalyzer intermittently crashed with a missing Get-Command, then shows how Copilot-assisted investigation, benchmarking, and targeted fixes turned it into a deterministic, faster analyzer with evidence reviewers can rerun.

Hidde de Smet lays out a practical way to judge whether a repo is actually ready for AI coding agents, using GitHub Copilot cloud agent as the concrete example. It focuses on repeatable setup, shared commands, focused tests, CI enforcement, and security boundaries so agent sessions aren’t wasted on missing prerequisites.

Jesse Houwing explains why GitHub Copilot cloud agent sessions can’t be spawned from GitHub Actions using GITHUB_TOKEN, and how GitHub’s accountability model (identity, billing, and auditability) shapes what “agentic workflows” can do today. He then lays out practical orchestration patterns that work, with concrete YAML examples.

Jesse Houwing explains how to stop GitHub Copilot agents from confidently inventing details about fast-moving tools by grounding them in a local clone of the real repository, then forcing answers to be backed by file-and-line citations from the source.

John Naguib explains a Copilot Studio billing change taking effect on September 1, 2026: existing agents and workflows built with the GitHub Copilot harness will start consuming Copilot Credits. The post breaks down what’s affected, how credit consumption works (authoring vs runtime), and what admins can review in PPAC to avoid cost surprises.

Hidde de Smet explains Agent Plugins 1.0, a small packaging standard that lets teams ship portable Agent Skills and MCP server definitions once, while keeping Copilot-specific extras in a namespaced folder. The post covers the required file layout, manifest and MCP schemas, and enterprise governance controls for plugin and MCP server policy.

DevClass reports on the Agent Plugins 1.0 specification, a cross-vendor effort to package agent skills and tool connectivity in a portable, file-system-based format. The goal is to make agent capabilities modular and reusable across compatible clients like VS Code and GitHub Copilot.

John Edward breaks down what GitHub Copilot does (and doesn’t) send to the service, how training and retention settings vary by subscription, and the practical security risks teams should plan for when using AI-assisted coding in real projects.