Conversation
Document /yolo as an interactive alias for /allow-all on, introduced in Copilot CLI v1.0.20. Key behavior: - /yolo and --yolo now behave identically - /yolo state persists across /restart Updates: - Chapter 01 slash commands table: add /yolo entry under Permissions - Appendix additional-context.md: add /yolo example in Inside a Session Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove note about state persistence across /restart.
Removed mention of state persistence for `/yolo` command.
There was a problem hiding this comment.
Pull request overview
Documents the /yolo slash command in the beginner course docs, aligning the slash-command reference and session examples with Copilot CLI v1.0.20 behavior.
Changes:
- Added
/yoloto the Chapter 01 “Additional Commands → Permissions” table as an alias for enabling auto-approval of permission prompts. - Updated the Chapter 01 caution note to mention both
/allow-alland/yolo. - Added an “Inside a Session”
/yoloexample to the additional context appendix.
Show a summary per file
| File | Description |
|---|---|
| 01-setup-and-first-steps/README.md | Adds /yolo to the slash command reference and updates the caution note. |
| appendices/additional-context.md | Adds an interactive /yolo example alongside other in-session permission commands. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
| |---------|--------------| | ||
| | `/add-dir <directory>` | Add a directory to allowed list | | ||
| | `/allow-all [on|off|show]` | Auto-approve all permission prompts; use `on` to enable, `off` to disable, `show` to check current status | | ||
| | `/yolo` | Quick alias for `/allow-all on` — auto-approves all permission prompts. | |
There was a problem hiding this comment.
The PR description says the /yolo documentation should note that its enabled state persists across /restart, but this isn’t mentioned anywhere in this chapter (there are no other /restart references). Consider adding that persistence note to the /yolo row (or nearby) to match the stated behavior in v1.0.20.
| |---------|--------------| | ||
| | `/add-dir <directory>` | Add a directory to allowed list | | ||
| | `/allow-all [on|off|show]` | Auto-approve all permission prompts; use `on` to enable, `off` to disable, `show` to check current status | | ||
| | `/yolo` | Quick alias for `/allow-all on` — auto-approves all permission prompts. | |
There was a problem hiding this comment.
This table’s descriptions generally don’t end with a period; the new /yolo row does. Consider dropping the trailing period to keep formatting consistent across the table.
| | `/yolo` | Quick alias for `/allow-all on` — auto-approves all permission prompts. | | |
| | `/yolo` | Quick alias for `/allow-all on` — auto-approves all permission prompts | |
What's New
Copilot CLI v1.0.20 (released 2026-04-07) made
/yoloand--yolobehave identically, and ensured/yolostate persists across/restart.Previously, the course only documented
--yolo(CLI flag) in the appendix automation section. The/yoloslash command for interactive sessions was undocumented.What Was Updated
1. Chapter 01 — Slash Commands Reference (
01-setup-and-first-steps/README.md)Added
/yoloas an entry in the Permissions table under Additional Commands:/allow-all on/restart/allow-alland/yolo2. Appendix — Additional Context (
appendices/additional-context.md)Added a
/yoloexample in the Inside a Session section showing beginners they can use it interactively without having to remember the longer/allow-all onform.Changes Not Made (and Why)
copilot mcpcommand/mcp enable/disablepersistencecopilot help monitoring(OpenTelemetry)Source
/yolo and --yolo now behave identically and /yolo state persists across /restart