Assisted permissions is generally available in Copilot CLI, the Copilot app and VS Code. It reduces approval prompts, but it is not the same as a sandbox.
Fewer interruptions, a different decision to make
GitHub’s 26 October release makes assisted permissions generally available in Copilot CLI, the Copilot app and Visual Studio Code. A language model assesses requests to run commands, access file-system paths or open URLs. Those judged clearly safe can proceed; others ask for approval. The important buying question is not simply whether this saves clicks. It is whether that level of delegation fits the workspace and the task.
Start somewhere you can afford to make a mistake
Our suggested first test is deliberately ordinary: ask Copilot to update a small test in a disposable copy of a project. Keep credentials, customer records and production access out of that workspace. Watch which requests proceed and which stop for a person. Then inspect the changed files and run the tests yourself. This is a proposed evaluation, not a HubAI test result or a claim that the permission classifier is infallible.
An approval decision is not an isolation boundary
It helps to separate two ideas. Permission handling decides whether an action should proceed. A sandbox restricts where an action can operate. Do not treat fewer prompts as evidence that a process cannot reach sensitive files or services. Ask your administrator what other boundaries are in place and keep the existing review before merging code. An apparently harmless command can still be inappropriate for a particular project.
Check the policy, not just the picker
GitHub says enterprise administrators can restrict Allow All and Assisted separately and choose a default for new sessions. A developer’s available choices still depend on policy. In the CLI, the entry point is /permissions; the app and VS Code have permission pickers. If your team changes mode, record the reason and a way back to manual approval. We verified the release notice, not your organisation’s effective settings. The cover is a conceptual illustration, not a product screenshot.
HUBAI VIEWBefore switching it on, try a small task in a disposable workspace and decide which actions still need a person.
Buyer decision signal: GitHub release · announced 26 October 2026
What to verify next
1Use a disposable project without private data.
2Observe automatic decisions and approval requests.
3Confirm enterprise restrictions with the administrator.
4Keep code review and a route back to manual approval.
Read the evidence
Capabilities, availability and prices can change. HubAI keeps analysis separate from the underlying official material.
01GitHub: assisted permissions release · 26 October 2026Open source ↗
Code AI
Code AI
Code AI