[bot] Update auto allow-all mode documentation: requires experimental mode#2239
Merged
aaronpowell merged 1 commit intoJul 9, 2026
Merged
Conversation
Per v1.0.69-3 (2026-07-07), the /allow-all auto mode now requires experimental features to be active (/experimental on or --experimental). The previous AUTO_APPROVAL env var approach has been removed. Update the auto allow-all mode note in Copilot Configuration Basics to document the experimental mode requirement and activation steps. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aaronpowell
approved these changes
Jul 9, 2026
Contributor
Author
|
🟡 Contributor Reputation Check: MEDIUM risk
Maintainers: please review this contributor before merging. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Learning Hub “Copilot Configuration Basics” documentation to reflect the Copilot CLI v1.0.69-3 behavior change where /allow-all auto now requires experimental mode.
Changes:
- Updated the “Auto allow-all mode (v1.0.69+)” callout to require enabling experimental mode (
/experimental onor--experimental) before using/allow-all auto. - Documented removal of the prior
AUTO_APPROVALenvironment variable approach. - Bumped
lastUpdatedto2026-07-07.
Show a summary per file
| File | Description |
|---|---|
| website/src/content/docs/learning-hub/copilot-configuration-basics.md | Updates the auto allow-all mode documentation and the page metadata to match the v1.0.69-3 behavior change. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Low
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
After reviewing GitHub Copilot releases from the past 7 days (June 30 – July 7, 2026), the Learning Hub pages are remarkably up to date. The one gap found is that the
auto allow-allmode documentation in Copilot Configuration Basics was missing a critical behavioral change introduced in v1.0.69-3 (released July 7, 2026).What changed
Release v1.0.69-3 (2026-07-07):
The auto allow-all mode (added in v1.0.69-1) uses an LLM judge to evaluate each tool request and auto-approve safe ones. In v1.0.69-3 this mode was moved behind the experimental flag, and the previous
AUTO_APPROVALenvironment variable approach was removed entirely.Section updated
website/src/content/docs/learning-hub/copilot-configuration-basics.md/experimental onor--experimental)/allow-all auto)AUTO_APPROVALenv var has been removedlastUpdatedto2026-07-07Other pages reviewed (no changes needed)
All other recent features from the past 7 days were already documented:
/mcp listwhile agent workingunderstanding-mcp-servers.mdstayInAutopilotsettingcopilot-configuration-basics.md/mcp managermid-turn toggleunderstanding-mcp-servers.mdkimi-k2.7-codemodel supportbuilding-custom-agents.mdSource announcement