GitHub makes Copilot assisted permissions generally available
GitHub announced on October 26 that assisted permissions are generally available in Copilot CLI, the Copilot app and Visual Studio Code. The mode evaluates requests to run commands, access file-system paths or open URLs. It is distinct from approving every action without review.
A large language model evaluates each permission request. Requests classified as clearly safe proceed automatically; other requests require the developer's approval. The announcement describes a classification system, not a guarantee that every permitted action is harmless or every risky action is detected.
In Copilot CLI, developers can run the permissions command and select assisted. The Copilot app exposes the choice through its mode picker and Tool permissions. In Visual Studio Code, the setting is available through the permissions picker. These are separate client interfaces for the permission mode.
Enterprise administrators can use managed settings to block Allow All while keeping Assisted available. They can also disable Assisted independently. Allowing this mode therefore does not require an organization to permit unrestricted execution.
Administrators can choose the default mode for new sessions, while developers can choose another mode allowed by policy. GitHub says a session starts with manual approval if the selected default is unavailable or prohibited. A default is not permission to override an enterprise restriction.
Teams should review the mode and applicable policy before relying on unattended actions. The release does not establish a universal list of safe commands, a measured security success rate or an exemption from reviewing sensitive requests. Assisted classification reduces some prompts but does not remove the need for access boundaries and judgment.