GitHub has made “Assisted” permissions generally available across Visual Studio Code, the GitHub Copilot CLI, and the Copilot desktop app, giving developers a middle ground between clicking “Approve” fifty times an hour and recklessly turning on “Allow All” mode. Instead of interrupting your workflow every time an AI coding agent wants to read a folder or run a safe unit test, Copilot now uses an AI safety evaluator to auto-approve clearly harmless requests while still pausing for human permission whenever a command touches sensitive files, system settings, or external URLs.
Anyone who has used an autonomous coding agent in the past year knows how quickly “approval fatigue” sets in. When you start a session in manual approval mode, the agent asks for permission to list files (ls), then asks again to search for a function (grep), then asks a third time to run a local test suite. After clicking “Yes” twenty times in ten minutes, most developers either stop reading the prompts closely or flip the switch to Allow All —giving the agent a blank check to run terminal commands unsupervised.
That “Allow All” habit has caused major headaches for IT security teams, because a single misunderstood prompt or hidden instruction in an untrusted repository can lead an unsupervised agent to delete local files, overwrite .env secrets, or send code to an external web address.
With GitHub’s new generally available Assisted permission tier, developers keep the speed of autonomous coding without handing over the keys to their machine. Routine, read-only, and clearly safe project commands run automatically in the background, so a human confirmation box only pops up when the request actually carries risk.
Fast Facts: How GitHub Copilot’s Assisted Permissions Mode Works
Release & Availability : Now generally available across Visual Studio Code , GitHub Copilot CLI , and the Copilot desktop app , as detailed in Visual Studio Magazine’s coverage of the GitHub release .What Gets Auto-Approved : Requests to run terminal commands, read/write project filesystem paths, or open URLs that the AI classifier evaluates as clearly safe proceed automatically without interrupting the user.What Still Requires a Human Click : Any command, outside folder access, or network URL request that isn’t classified as clearly safe pauses execution and prompts the developer for manual approval.How to Turn It On :Copilot CLI : Type /permissions and select assisted.VS Code : Select Assisted directly from the agent permissions picker in the chat/agents panel.Copilot App : Toggle Assisted under Tool permissions in settings.Enterprise Admin Controls : Organization administrators can now block Allow All across the entire company while allowing developers to use Assisted, or disable Assisted separately; if a configured default is blocked by policy, new sessions safely fall back to Manual approval .
Permission Mode Comparison: Manual vs. Assisted vs. Allow All
The table below shows how the three permission modes in GitHub Copilot compare for daily coding speed and workstation safety.
Permission Setting
What Happens on Safe Commands (git status, npm test, reading repo files)
What Happens on Risky Commands (rm -rf, reading ~/.ssh, calling external URLs)
Best For
Manual Approval Stops and asks the user to click Approve every single time
Stops and asks the user to click Approve
Auditing untrusted third-party repos or highly sensitive production servers
Assisted Permissions (New GA) Proceeds automatically in the background with zero popup frictionPauses and prompts the user for explicit confirmationEveryday development — eliminates approval fatigue while catching dangerous actions
Allow All Proceeds automatically
Proceeds automatically without asking (High security risk)Ephemeral throwaway cloud containers only; should be blocked on employee laptops
Manual Approval
What Happens on Safe Commands (git status, npm test, reading repo files) Stops and asks the user to click Approve every single time
What Happens on Risky Commands (rm -rf, reading ~/.ssh, calling external URLs) Stops and asks the user to click Approve
Best For Auditing untrusted third-party repos or highly sensitive production servers
Assisted Permissions (New GA)
What Happens on Safe Commands (git status, npm test, reading repo files) Proceeds automatically in the background with zero popup friction
What Happens on Risky Commands (rm -rf, reading ~/.ssh, calling external URLs) Pauses and prompts the user for explicit confirmation
Best For Everyday development — eliminates approval fatigue while catching dangerous actions
Allow All
What Happens on Safe Commands (git status, npm test, reading repo files) Proceeds automatically
What Happens on Risky Commands (rm -rf, reading ~/.ssh, calling external URLs) Proceeds automatically without asking (High security risk)
Best For Ephemeral throwaway cloud containers only; should be blocked on employee laptops
Why “Assisted” Mode Fixes the Biggest Real-World Security Gap in AI Coding
In enterprise security audits, the biggest danger with AI coding tools rarely comes from sophisticated hackers—it comes from busy developers trying to get their work done before a deadline. When an editor only offers two extremes—Manual (which interrupts you every 15 seconds) or Allow All (which never interrupts you)—human nature guarantees that most people will eventually pick Allow All just to stay in flow.
Once a developer turns on Allow All on their work laptop, two everyday accidents happen regularly:
Accidental Destructive Cleanup : An agent trying to fix a build conflict decides to run git reset --hard, rm -rf dist/, or drop a local development database table without asking first.Untrusted Repo Prompt Injection : A developer clones an open-source repo or inspects a pull request containing hidden instructions in a README or test fixture that tell the agent to curl local environment variables to an external URL.
GitHub’s Assisted tier breaks that all-or-nothing trade-off in two practical ways:
First, for the individual developer, it silences 80% to 90% of the harmless “Can I read this file?” and “Can I run the linter?” popups. Because your screen only flashes an approval dialog when the agent wants to do something unusual—like reach outside your project folder, install an unfamiliar package, or open an external web link—you actually pay attention when the prompt appears.
Second, for company IT administrators, GitHub separated the policy switches for Allow All and Assisted. Previously, if a security team banned automatic execution to protect company laptops, developers were forced back into frustrating 100% manual mode. Now, admins can ban Allow All organization-wide while setting Assisted as the default
Setting up Assisted permissions takes less than two minutes whether you code alone or manage a 200-person engineering team.
The 4-Step Enterprise Implementation Playbook
Ban Allow All in GitHub Organization Settings and Set Assisted as Default : If you manage a GitHub Enterprise or Team organization, open your Copilot policy settings today, disable the Allow All option across all seats, and set Assisted as the default permission mode for new sessions. Any environment where Assisted is restricted will automatically fall back to safe Manual mode.Switch Your Local Copilot CLI via /permissions : If you use GitHub Copilot in the terminal, launch a session, type /permissions, and switch from Manual or Allow All to assisted. This lets the CLI inspect logs and run build checks smoothly while still stopping before running destructive shell commands.Select Assisted in the VS Code and Desktop App Pickers : In Visual Studio Code, click the permissions picker inside the Copilot / Agents panel and select Assisted ; in the standalone Copilot desktop app, enable it under Tool permissions .Drop Back to Manual When Opening Untrusted Third-Party Code : Even with Assisted mode enabled, keep a simple personal rule: whenever you clone an unfamiliar external repository or inspect a stranger’s pull request, flip the picker back to Manual for that session so not a single command or URL runs without your explicit click.
Check If You Left Allow All Turned On : Open VS Code and the Copilot CLI (/permissions) on your laptop today; if you previously switched on Allow All out of frustration with constant popups, step it down to Assisted immediately.Update Organization Policy Defaults : IT and DevSecOps leads should log into GitHub admin settings, block Allow All for non-containerized developer workstations, and enable Assisted so teams don’t rebel against security controls.Review What Triggers Manual Prompts : During your first day using Assisted mode, note which commands still trigger a confirmation dialog—they are a great real-time lesson in where your AI agent is reaching outside the project sandbox.
Beat:
Topics:
# agent-governance
# ai-security
# copilot-cli
# developer-tools
# github-copilot
# vs-code
