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.
Copilot in Visual Studio Adds PR Exploration, a BYOM Migration, and NuGet Fixes
GitHub summarized three September updates for Copilot in Visual Studio 2026 on October 22, 2026. The Git agent can explore an attached pull request and link back to comments and files. Bring Your Own Model remains in preview but now requires the new Agent experience, and previously configured Ollama models must be added again. NuGet Audit warnings can open Copilot Chat with the NuGet MCP server to propose dependency fixes. This article gives .NET developers a cautious upgrade checklist: preserve current settings, validate each feature independently, review package and lock-file changes, run targeted tests and vulnerability scans, and keep a rollback path. Summaries and suggested fixes remain review inputs, not verified outcomes.
Bayer Shares Production Lessons From 22 Specialist Agents: HTTP Success Is Not Task Success
AWS published Bayer Crop Science’s Agentic Decision Engine case study on October 23, 2026. The production system runs 22 specialist agents over governed analytics workflows, models, logs, and visualization tools. This article turns the architecture into five reusable acceptance checks for enterprise agent teams: persist the state needed to resume work, define identity and authorization at every boundary, scope each agent’s tool catalog, distinguish transport success from task success, and release to a gated group before broader access. It also explains why Bayer’s adoption and resolution figures are evidence about one implementation, not promises for another organization. The focus is operational proof, least privilege, rollback, and observable outcomes rather than prompt polish.
GitHub Copilot in Teams Turns Notifications Into Pull Requests: What to Check Before Review
GitHub updated its Microsoft Teams app on October 23, 2026, so an issue notification in a channel, group chat, or private chat can become a Copilot task that investigates the problem, proposes a fix, and opens a pull request. This article helps development and product teams adopt the workflow without mistaking an automated pull request for shipped code. It explains the consolidated app, repository connection, the November 16 retirement of the legacy GitHub app, and the review boundary. A practical acceptance checklist asks teams to reproduce the issue, inspect changed files, run targeted tests, verify permissions, and keep merge and deployment as explicit human decisions.
IskayPet Connects SharePoint to a Managed Knowledge Base: Validate Permissions Before Answers
AWS published IskayPet’s corporate knowledge assistant case study on October 22, 2026. The system connects Amazon Bedrock Managed Knowledge Bases to existing SharePoint repositories and answers cited questions across retail operations, veterinary care, onboarding, and procurement in four languages and three countries. This article turns the case into a practical acceptance plan for knowledge owners. It checks source scope, inherited permissions, hybrid retrieval, duplicate and fragment removal, citation quality, feedback, and token cost before expansion. It also separates the customer’s reported production results from what another organization should expect. A managed retrieval stack reduces infrastructure work, but it does not remove content ownership, access reviews, evaluation datasets, or human verification of important answers.
GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts
GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.
Summary
GHES 3.22 RC moves Copilot CLI into isolated environments, but offline confidence comes from combined endpoint, network, permission, audit, and recovery evidence.