GitHub Models Is Retired as Copilot CLI and AI Credit Migration Moves Into Execution
The playground, model catalog, inference API, and BYOK have stopped, so ENHE's July 3 preview is updated with the confirmed status and a migration checklist
Key takeaways
GitHub Models was fully retired on July 30, 2026. The playground, model catalog, inference API, and bring-your-own-key access are no longer available, including for customers with active usage. ENHE's July 3 page had already documented the announced retirement date; this update changes the event from a future plan to a confirmed production state and adds migration checks. GitHub points users who need direct model access toward Microsoft Foundry and users building AI workflows on GitHub toward GitHub Copilot. Teams should inventory endpoints, keys, billing ownership, rate limits, model behavior, and rollback paths before replacing the retired service. The Copilot CLI and AI credit guidance remains relevant for governed automation.
# GitHub Models Is Retired as Copilot CLI and AI Credit Migration Moves Into Execution
Published or updated: July 31, 2026
Table of contents
- Direct answer
- Fact sources
- Action steps
- Why it matters
- Impact for ordinary AI users
- Related tools and tutorials
- FAQ
- Source links
Direct answer
GitHub Models is now retired. As of July 30, 2026, the playground, model catalog, inference API, and BYOK are unavailable to both new and existing customers. Projects that need direct model access can evaluate Microsoft Foundry, while users building AI workflows inside GitHub can evaluate GitHub Copilot. The two paths differ in model scope, billing, credentials, permissions, and rate limits.
Fact sources
GitHub published the final retirement notice on July 30, 2026. It says the GitHub Models playground, model catalog, inference API, and BYOK are no longer available to any customer, including existing customers with active usage. This completes the retirement announced on July 1.
GitHub separates the migration guidance into two paths. Projects needing direct model access can review the Microsoft Foundry model catalog. Users building AI-powered workflows directly on GitHub can evaluate GitHub Copilot. The announcement does not claim identical models, APIs, pricing, or compatibility.
ENHE first published this page on July 3 to explain Copilot CLI, AI credit session limits, cost centers, and the scheduled GitHub Models retirement. July 30 was still in the future then. This update changes the retirement from a plan to a confirmed state while preserving the same CMS record and canonical slug.
How to check a migration after GitHub Models retirement
- Inventory every GitHub Models playground workflow, inference endpoint, BYOK credential, model name, repository script, and test-environment reference.
- Separate direct model API needs from AI workflows inside GitHub, then evaluate Microsoft Foundry and GitHub Copilot for their respective tasks.
- Recheck authentication, secret storage, model regions, pricing, rate limits, data retention, and organization billing ownership.
- Use a fixed evaluation set to compare replacement-model output, latency, tool calls, error formats, and safety behavior.
- Add explicit failures and removal dates for retired endpoints so scripts do not silently retry or fall back to an unknown model.
- Switch production workflows only after permissions, cost limits, logs, tests, review, and rollback are verified.
Why it matters
The move from retirement notice to completed shutdown shows that a public model playground cannot be treated as permanent infrastructure. Migration is more than replacing a URL; it includes model behavior, authentication, cost, data boundaries, errors, and organizational ownership. This page retains its Copilot CLI and AI credit guidance because governed automation still needs session limits, repository permissions, and review records.
Impact for ordinary AI users
Users who relied on GitHub Models for comparisons, prototypes, or BYOK should check scripts, extensions, and tutorials for retired references. Users who never used the service do not need to migrate, but the shutdown is still a useful selection lesson: experimental entry points, production APIs, billing accounts, and long-term support must be evaluated separately.
Related tools and tutorials
ENHE's AI news tracks service status, the software catalog supports replacement comparisons, skill tutorials cover migration tests, and account services help users check credentials, permissions, and billing ownership.
AI service status and current news; AI model and software comparisons; AI migration tests and skill tutorials; AI credentials, permissions, and billing services.
FAQ
Can GitHub Models still be used?
No. GitHub says the playground, model catalog, inference API, and BYOK have been unavailable to all customers since July 30, 2026.
Is Microsoft Foundry or GitHub Copilot the direct replacement?
It depends on the task. Microsoft Foundry is a path for direct model access and catalog needs. GitHub Copilot is a path for AI inside GitHub development workflows. They are not the same product.
Do AI credit session limits still matter?
Yes. GitHub Models retirement does not end Copilot CLI or SDK usage. Copilot automation still needs usage limits, permissions, logs, and human review.
Source links
- GitHub Changelog：GitHub Models is now retired（2026-07-30）
- GitHub Changelog：GitHub Models is being fully retired on July 30, 2026（2026-07-01）
- Microsoft Foundry：Models catalog
- GitHub Docs：GitHub Copilot
- GitHub Docs：Use your own API keys with Copilot
- GitHub Blog：Copilot usage-based billing
What this means for everyday users
ENHE users should inventory retired GitHub Models endpoints, model names, and BYOK references, then document authentication, pricing, rate limits, data boundaries, and human review for each replacement.
Related reading
GitHub adds enterprise controls for Copilot agent commands, files, and network access
GitHub released enterprise-managed permissions for Copilot agent operations on September 9. Administrators can centrally set shell commands, file reads and writes, and access to network domains to blocked, approval required, or allowed without a prompt. User preferences, workspace settings, automatic approval, and earlier approvals cannot make the enterprise policy less restrictive. GitHub says the controls are generally available in the Copilot app, Copilot CLI, and Visual Studio Code sessions that use Agent Host for Copilot Business and Enterprise customers. Security and platform teams should begin with a minimum-permission baseline, test representative repositories, and expand only the operations that have a clear owner, audit trail, and rollback path.
AWS Launches AgentCore Evaluations for Testing Any Agent Framework
AWS Launches AgentCore Evaluations for Testing Any Agent Framework. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: establishing repeatable offline evaluations, online monitoring, and human spot checks for an AI agent. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
How to Build an AI Agent Evaluation Baseline: From Offline Tests to Production Review
How to Build an AI Agent Evaluation Baseline: From Offline Tests to Production Review. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: establishing a repeatable baseline for AI-agent quality, risk, cost, and human review. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
SageMaker AI Adds Script Mode in SDK v3 for Bring-Your-Own-Model Training
SageMaker AI Adds Script Mode in SDK v3 for Bring-Your-Own-Model Training. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: migrating an existing training script to SageMaker while verifying dependencies, data, and cost. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
AWS AgentCore Adds Cross-Account Knowledge Base Connections
AWS AgentCore Adds Cross-Account Knowledge Base Connections. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: enabling an AI agent to securely retrieve from a knowledge base in another account while verifying least-privilege access. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
GitHub Makes Global Model Policy Generally Available for Copilot
GitHub Makes Global Model Policy Generally Available for Copilot. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: standardizing Copilot model access rules across a team while preserving evidence of policy changes. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
Summary
A reliable migration begins with an inventory of retired dependencies, then separates direct model access from AI workflows inside GitHub. The move is complete only when replacement permissions, cost, behavior, and rollback have been verified.
