What happened
GitHub’s Copilot CLI release notes identify version 1.0.111 as released on November 13, 2026. The headline change is regular-expression support for enterprise-managed Shell, Bash, and PowerShell permission rules. The notes do not describe the matching syntax, configuration format, precedence, or evaluation behavior; they state that regex support has been added to these managed rules. The change is specifically about enterprise-managed permissions, not a general announcement that every shell command is now governed by a new policy system.
A second named addition is the --host-allow-session-creation option. GitHub says it lets remote clients create sessions on CLI hosts for one launch without changing saved settings. The release note establishes that bounded behavior, but does not give examples of the client setup or describe how an administrator enables or restricts the option. The important distinction is that the session-creation allowance is described as applying to one launch, rather than rewriting the host’s saved configuration.
The same release refreshes premium-request usage in /usage so that percentages stay current. The rest of the release notes list a wide range of interface, shell, session, MCP, plugin, workflow, and reliability changes. Among them are preventing duplicate MCP OAuth reconnects, preserving servers in a needs-auth state after canceled authorization, letting /mcp delete remove a server without restarting other connected MCP servers, and preserving background sessions during session deletion or pruning. These are individual changes in the CLI rather than a single new feature announcement.
The permission-rule and remote-session additions are the changes most relevant to teams operating the CLI under managed controls. GitHub does not give a version-specific price, a rollout schedule, or account eligibility details in the release entry. The page identifies the release as 1.0.111 and lists its commit as 3bb7267; it does not provide a separate installation guide for the two additions.
What the archive adds
New Runtime covered GitHub’s startup policy-refresh enforcement and minimum client-version enforcement for the Copilot sandbox key on October 30, 2026. It also covered Copilot CLI 1.0.109’s CIDR sandbox rules on November 10, 2026. This is a new fact in the ongoing story of enterprise controls around the CLI: regex joins the recently added network-range rules.
Trend signal
This update supports agent security moves to runtime boundaries: enterprise-managed permission rules constrain an agent’s access at the point where it can use shell tools, rather than relying only on instructions in a prompt. The release does not establish how comprehensive or effective those controls are, so it is evidence of a product direction, not proof that runtime risks have been solved.
Why now
The update follows two recent Copilot CLI control changes. New Runtime’s October 30, 2026 coverage described startup policy-refresh and minimum-client-version enforcement for the sandbox key. Its November 10, 2026 note described CIDR sandbox rules. Version 1.0.111 arrives three days later with regex matching for managed shell rules, extending the set of centrally managed constraints without GitHub presenting the release as a single unified enterprise-security launch.
Connections to other events
New Runtime’s earlier coverage of version 1.0.109 described IPv4 and IPv6 CIDR sandbox rules, while this release adds matching flexibility to Shell, Bash, and PowerShell permissions. A separate November 6, 2026 note on apexe 0.10.0 covered governed shell and agent setup across several coding-agent tools. Together, these events point to governance moving into the execution environments and permissions around agents, though they are separate products with different control models.
Why it matters
Shell access is one of the consequential permissions in a coding-agent workflow: it can let an agent run commands in a repository and its surrounding environment. Enterprise-managed rules give organizations a way to set boundaries centrally. Adding regex matching can make those rules more expressive, which may help administrators describe classes of commands without maintaining only exact command strings. The source does not explain the matching semantics, so teams should not assume that a particular pattern is safe or behaves as expected until they test it.
The one-launch session option addresses a different operational need. It allows remote clients to create a session on a CLI host without changing saved settings. For teams that use remote clients, keeping that permission scoped to a launch could make a temporary workflow easier to authorize. The release note does not say that this flag replaces existing policy controls; teams should treat it as a specific option to evaluate alongside their current configuration.
Limits and uncertainty
GitHub’s release notes announce regex support but do not specify the regex dialect, escaping rules, rule ordering, or how a match interacts with other permission decisions. They also do not provide examples, security testing results, or guidance for migrating existing rules. The description of --host-allow-session-creation does not identify supported remote clients or explain the authorization flow. The announcement makes no claims about measured security outcomes or changes in access for particular enterprise plans. Teams should verify these behaviors in their own CLI configuration before relying on them as a security boundary.
Skill to build now
Create a small non-production repository and exercise the managed shell rules your organization expects to use. Test intended allowed and denied command forms, including variations in arguments and quoting, then record the observed result and the CLI version. Separately, try the one-launch remote-session flag in the workflow where a remote client would create a host session. This makes the release’s stated capabilities concrete before they become part of a broader agent-access policy.
Reader takeaway
Copilot CLI 1.0.111 gives enterprise administrators a more expressive way to write managed shell permission rules and adds a one-launch remote session-creation option. Both changes are useful to evaluate in controlled configurations, but the release note is not a policy specification. Test how patterns actually match before using them to define production boundaries.