From f0a90ab9a561ec2791efed9b416f8756a08e902e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 15 Jul 2026 21:03:37 +0000 Subject: [PATCH] Update Learning Hub for Copilot CLI v1.0.71 changes - Fix /worktree and /move documentation: split into separate commands (/worktree leaves uncommitted changes behind, /move carries them) - Add /voice and /voice devices documentation (v1.0.71+) - Add canvas support in CLI section to working-with-canvas-extensions.md (v1.0.71+) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../copilot-configuration-basics.md | 21 ++++++++++++++----- .../working-with-canvas-extensions.md | 6 +++++- 2 files changed, 21 insertions(+), 6 deletions(-) diff --git a/website/src/content/docs/learning-hub/copilot-configuration-basics.md b/website/src/content/docs/learning-hub/copilot-configuration-basics.md index 6dac387bc..eacca8627 100644 --- a/website/src/content/docs/learning-hub/copilot-configuration-basics.md +++ b/website/src/content/docs/learning-hub/copilot-configuration-basics.md @@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics' description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-07-13 +lastUpdated: 2026-07-15 estimatedReadingTime: '10 minutes' tags: - configuration @@ -541,21 +541,23 @@ The `/cd` command changes the working directory for the current session. Since v This is useful when you have multiple backgrounded sessions each focused on a different project directory. -The `/worktree` command (v1.0.61+, also aliased `/move`) creates a new git worktree and switches into it, moving any uncommitted changes along. This lets you start working on a parallel branch without leaving your current terminal session: +The `/worktree` command (v1.0.61+) creates a new git worktree on a fresh branch and switches the session into it. Since v1.0.71, `/worktree` **leaves your uncommitted changes behind** in the current worktree — use `/move` when you want to bring them along: ``` -/worktree my-feature-branch +/worktree my-feature-branch # create worktree, leave uncommitted changes behind +/move my-feature-branch # create worktree, carry uncommitted changes into it ``` -In v1.0.66+, you can pass a task description to `/worktree` to name the branch from the task and immediately run the task as the first prompt in the new worktree — all in one step: +In v1.0.66+, you can pass a task description to either command to name the branch from the task and immediately run the task as the first prompt in the new worktree — all in one step: ``` /worktree fix the login redirect +/move fix the login redirect ``` This creates a branch named from your task description and begins working on it immediately, making it easy to spin up parallel work without stopping to think of a branch name. -After the command runs, the session is inside the new worktree. Use this when you want to work on a second task in parallel without stashing changes or opening a new terminal. In v1.0.64+ you can also use the experimental `--worktree` flag at startup (`copilot -w [name]`) to create or reuse a worktree under `.worktrees/` before the session begins. +After either command runs, the session is inside the new worktree. Use `/worktree` to start fresh on a parallel task, and `/move` when you've already begun work locally and want to continue it on its own branch. In v1.0.64+ you can also use the experimental `--worktree` flag at startup (`copilot -w [name]`) to create or reuse a worktree under `.worktrees/` before the session begins. The `/every` command (also available as `/loop` since v1.0.64) schedules a recurring prompt to run automatically at a specified interval. The companion `/after` command runs a prompt once after a specified delay. Both are useful for self-paced automation — polling for results, periodically summarizing progress, or triggering other slash commands on a timer: @@ -647,6 +649,15 @@ The `/refine` command *(v1.0.70+)* rewrites a rough, stream-of-consciousness pro Type your rough idea, and `/refine` transforms it into a precise, well-structured prompt. This is especially helpful for complex multi-step tasks where prompt clarity significantly affects output quality — for example, turning "um make the login thing work better with the existing setup" into a focused task description with clear scope and acceptance criteria. +The `/voice` command *(v1.0.71+)* enables voice input mode, letting you speak prompts instead of typing them. The `/voice devices` subcommand opens a picker to choose and persistently save which microphone to use for voice input: + +``` +/voice # start voice input mode +/voice devices # choose and persist your microphone +``` + +This is useful when you want to dictate long or complex prompts quickly, or when your hands are occupied with other work. Your microphone selection persists across sessions so you don't need to re-configure it each time you use voice mode. + The `/env` command shows all loaded environment details — instructions, MCP servers, skills, agents, and plugins — in a single view. Use it to verify that the right resources are active for the current session: ``` diff --git a/website/src/content/docs/learning-hub/working-with-canvas-extensions.md b/website/src/content/docs/learning-hub/working-with-canvas-extensions.md index 2c577027c..6230c7d47 100644 --- a/website/src/content/docs/learning-hub/working-with-canvas-extensions.md +++ b/website/src/content/docs/learning-hub/working-with-canvas-extensions.md @@ -3,7 +3,7 @@ title: 'Working with Canvas Extensions' description: 'Create and iterate on GitHub Copilot app canvases using /create-canvas, then shape them into reusable project or personal extensions.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-06-17 +lastUpdated: 2026-07-15 estimatedReadingTime: '8 minutes' tags: - copilot-app @@ -22,6 +22,10 @@ Canvas extensions give you shared, interactive work surfaces inside the GitHub C This guide explains what canvases can do, how to create one with `/create-canvas`, and how to use patterns from this repository as reference implementations. +## Canvas support in Copilot CLI + +*(v1.0.71+)* Canvas extensions are now also supported in **GitHub Copilot CLI** — not just in the Copilot desktop app. This means extension-driven canvases you build can surface panel-style UIs and callable capabilities directly within CLI sessions. The development and iteration workflow described below (using `/create-canvas` in the app) remains the recommended authoring experience; CLI support means those same extensions can be loaded and used when working from the terminal. + ## What canvases can do A canvas is a bidirectional surface: