Coding Tools
GitHub Copilot Code Review API and Default Effort Change
GitHub Changeloghigh confidence
Why it matters
- →API access allows Copilot code review to be integrated into CI/CD pipelines and custom automation scripts.
- →Default effort level shifts to Balanced, changing the baseline behavior for most repositories.
- →Programmatic control enables teams to standardize code review processes across organizations.
GitHub has made Copilot code review generally available through REST and GraphQL APIs, allowing developers to trigger reviews programmatically from scripts and internal tools. The update also changes the default review effort level to Balanced for new and existing repositories, replacing previous defaults while respecting explicit Lite settings. These features are now available across Copilot Pro, Pro+, Max, Business, and Enterprise plans. The API integration enables automated code quality checks within continuous integration workflows.
Read originalThe story around this
Earlier coverage that leads up to this article, and what followed. Lines connect each piece to the closest one after it, converging here.
How we got here
- 1GitHub Releases Copilot App for Desktop
Matt Wolfe · June 5, 2026 · Related
- 2GitHub Copilot Enhances Code Review Efficiency
GitHub Changelog · June 25, 2026 · Same story
- 3GitHub Copilot Enhances Code Review Automation
GitHub Changelog · September 11, 2026 · Same story
Follow this story
Open the full story →GitHub Copilot adds in-product settings validator
2 developments
- Sep 25 · GitHub Changelog
GitHub Copilot adds in-product settings validator - Oct 2 · GitHub Changelog
GitHub Copilot Code Review API and Default Effort Change (This article)↳ GitHub exposes Copilot code review via REST and GraphQL APIs for automation while shifting the default effort level to Balanced.
More from GitHub Changelog
© GitHub ChangelogCoding Toolscoding
GitHub Copilot deprecates specific models
GitHub quietly retired several underlying models for Copilot Chat and code completions, forcing a shift in the default inference stack. Enterprise admins must now manually enable alternative models via policy settings to maintain access, turning what was once automatic into an administrative task. This signals that GitHub is actively pruning its model portfolio rather than just adding new ones, likely to consolidate costs or improve quality control. Developers relying on specific legacy behaviors may find their workflows broken until policies are updated.
GitHub Changelog
© GitHub ChangelogCoding Toolscoding
GitHub GraphQL API expands SecurityAdvisory fields
GitHub’s GraphQL API now exposes critical vulnerability metadata directly, eliminating the need to fall back to REST for basic advisory data. Five new fields like cveId and nvdPublishedAt allow developers to pull CVE identifiers and NVD publication times in a single query. The addition of severities and isWithdrawn filters enables server-side narrowing, which significantly reduces client-side processing and rate limit consumption. This consolidation streamlines security integrations by unifying authentication paths and simplifying the construction of triage feeds.
GitHub Changelog
© GitHub ChangelogCoding Toolscoding
GitHub adds confidential comments to security advisories
Security triage just got a much-needed privacy layer. GitHub now allows maintainers to post confidential comments on repository security advisories, visible only to those with write access. This solves the awkward workflow of moving sensitive investigation details or abuse reports off-platform to keep them away from reporters and external collaborators. The feature respects existing permissions and logs views in the audit trail, making internal coordination seamless without exposing strategic discussions.
GitHub Changelog
More in Coding Tools
Coding Toolscoding
Claude Code v2.1.288 fixes resume and MCP bugs
This release stabilizes the core session management of Claude Code, specifically targeting the fragile state of resumed conversations where context or thinking traces were previously lost. It also patches critical reliability issues in the Model Context Protocol (MCP) integration, ensuring tool calls don't duplicate or hang indefinitely when remote servers misbehave. The addition of $.ui.selection() for mods and better GitHub CLI handling in cloud sessions shows a focus on developer workflow friction rather than new capabilities. These are necessary maintenance updates that make the tool more robust for heavy daily use.
Claude Code Releases
Coding Toolscoding
Claude Code v2.1.289 patches sandbox and plugin stability
This release is a classic maintenance patch for Claude Code, focusing on stabilizing the terminal interface and tightening security rules. It fixes critical bugs where deny/ask rules were bypassed in nested shell commands or via symlinks, ensuring sandbox policies actually hold. The update also resolves numerous UI freezes caused by malformed HTML tags and plugin rendering errors, making the agent feel less brittle during complex coding sessions.
Claude Code Releases
Coding Toolscoding
llama.cpp b11372 optimizes Qwen4-Exp memory and GPU support
This release tackles the notorious memory hunger of long-context inference for Qwen4-exp models by halving indexer score memory. The optimization works by computing head scores in place rather than materializing separate tensors, a change that significantly reduces VRAM pressure during heavy workloads. Beyond memory efficiency, b11372 expands hardware coverage with CUDA 13 support and Vulkan tiling for the lightning indexer. It also adds ROCm 10.0 binaries, keeping AMD users in step with NVIDIA's latest driver ecosystem. The result is a leaner runtime that handles extended contexts without hitting out-of-memory errors as quickly.
llama.cpp Releases