Copilot CLI 1.0.111 adds regex-based permission rules and a one-launch remote-session path. For a client build, the useful question is which commands may run, where they may run and how the handoff is closed.
What changed
The official release describes enterprise-managed Shell, Bash and PowerShell permission rules with regular expressions, plus a one-launch remote-session path. This is CLI functionality, not a general Copilot web or API change.
Write the policy before the task
In a disposable development repository, name the allowed command family, denied command family, working directory, session lifetime and rollback owner. Exclude credential export, destructive filesystem actions and unbounded network tools.
Run a bounded pilot
Use a typecheck or static build on a non-production remote host. Confirm that an allowed command runs, a non-matching command is denied or asks for approval, and the session ends with an identifiable result. Capture the policy, task identifier, host identity and output status.
Hand back a policy diff
The client should receive the exact CLI version, shell and host platform, regex rules, new-command behavior and stop procedure. A permission policy is part of the delivery artifact.
Limits
Availability depends on the client's Copilot CLI, enterprise and remote-host configuration. No client environment was accessed.