GitHub Enterprise Server 3.22 RC Brings Copilot CLI to Isolated Environments
The technical preview can use an enterprise model provider without GitHub Cloud, but offline claims still depend on endpoint and network evidence.
Key takeaways
GitHub released the Enterprise Server 3.22 candidate on August 11, 2026 with a technical preview that lets administrators configure Copilot CLI for enterprises operating without connectivity to GitHub Cloud. Users can authenticate with GHES credentials and use the configured model provider. GitHub's Copilot CLI documentation adds an important boundary: offline mode provides full network isolation only when the provider is also local or inside the isolated environment. If the provider base URL is remote, prompts and code context still travel to that provider. Teams should validate a test instance, model tool calling and streaming, certificates, DNS, proxies, outbound rules, repository permissions, audit logs, failure handling, upgrades, and rollback before considering production use.
# GitHub Enterprise Server 3.22 RC Brings Copilot CLI to Isolated Environments
August 16, 2026
Direct answer
GHES 3.22 RC enables an isolated Copilot CLI preview, but real offline operation depends on the model endpoint and network path. Test it outside production first.
Fact sources
GitHub published the GHES 3.22 release candidate on August 11, 2026.
The candidate lets administrators configure a model provider for Copilot CLI without GitHub Cloud connectivity, using GHES credentials.
GitHub says remote provider endpoints still receive prompts and code even when Copilot CLI offline mode is set.
Six acceptance checks for an isolated pilot
- Create a non-production GHES 3.22 RC instance with backup and rollback.
- Map provider location, domains, certificates, DNS, proxy, and outbound rules.
- Validate tool calling, streaming, context, and allowed models.
- Test GHES credentials, repository scope, MCP, shell, and file permissions.
- Verify prompt, code, tool, error, usage, and administrator audit logs.
- Drill provider failure, certificate expiry, failed upgrade, and workflow fallback.
Why it matters
An offline flag does not prove every model request, telemetry path, plugin, or tool stays inside the network. A release candidate and technical preview also carry change risk.
Impact for ordinary AI users
Disconnected teams gain a coding-agent pilot path, while operations teams inherit model, certificate, network, logging, and upgrade work. Developers still need repository controls and human review.
Related tools and tutorials
Start with one reversible task, verify version, permissions, cost, logs, and accepted output, then record the result in a team checklist.
AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news
FAQ
Does offline mode guarantee that code stays inside?
No. A remote provider still receives prompts and code context.
Is GHES 3.22 RC production-ready?
Treat the candidate and preview as controlled test material until acceptance evidence exists.
Can every internal model work?
The model must support compatible tool calling and streaming, with sufficient context and stability.
Source links
- GitHub Changelog: GHES 3.22 release candidate (2026-08-11)
- GitHub Docs: GHES 3.22 release notes
- GitHub Docs: Use your own models in Copilot CLI
- GitHub Docs: Administer Copilot CLI
What this means for everyday users
Record GHES version, provider, network map, certificates, DNS, proxy, egress, credentials, repository scope, tools, MCP, logs, backup, drill, and rollback owner.
Related reading
From Chat Boxes to Personal AI Companions: AI Assistants Are Entering the Desktop Execution Era
AI assistants are moving from answering questions toward continuing real tasks. AI agents, MCP tool ecosystems, personal memory, and local workbenches are pushing this shift together. For users, the real value is not another chat box, but less repeated context setup and more continuity from thinking to doing.
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.
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.
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.
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.
Summary
GHES 3.22 RC moves Copilot CLI into isolated environments, but offline confidence comes from combined endpoint, network, permission, audit, and recovery evidence.
