Verified, then logged.
Sun 22 Nov 2026 · 00:28 KST / 15:28 UTC한국어 | ENSearch /

02 / IT · Analysis

Copilot CLI adds regex rules for enterprise shell access

The update expands command permission rules, fixes the order of follow-up instructions and preserves saved settings when configuration files cannot be read.

An enterprise administrator works with a terminal and shell execution permissions panel on two monitors, with screen content and facial details obscured. AI-generated image

GitHub announced regular expression support in Copilot CLI 1.0.111 for enterprise-managed shell permission rules.

GitHub also reported fixes to queued instructions and saved settings. Together, these changes address which commands developers can run and how their work continues between instructions.

The release notes also distinguish permissions by scope. GitHub added temporary permission for remote session creation and restricted workflows from starting copies of themselves.

Enterprise command permissions

GitHub said enterprise-managed Shell, Bash and PowerShell permission rules now support regular expressions, patterns used to match text. This expands how enterprises can define command permissions.

The release notes name --host-allow-session-creation as the option for allowing remote clients to create sessions on CLI hosts. The permission applies to a single launch without changing saved settings.

The order of follow-up instructions

GitHub said it fixed the execution order of follow-up instructions entered while the agent is working. They now run in the order entered, including instructions that reach a session between turns and previously could be overtaken by later instructions.

GitHub also added a restriction to experimental dynamic workflows. A workflow's own agent can no longer start or resume workflow runs, preventing it from starting unlimited copies of itself when all tools are allowed.

Settings preserved after configuration errors

GitHub said it fixed startup behaviour that replaced an unreadable config.json with a new file. Existing saved content, including trusted folders and plugins, now stays in the file.

According to the release notes, plugin commands now fail and identify config.json when the file cannot be parsed. Previously, they could report success without making a change.

These changes preserve saved configuration content and make plugin command failures explicit. GitHub did not disclose a procedure in the release notes for automatically repairing the contents of a damaged configuration file.