[bot] Document Copilot app v1.1.26 and v1.1.24 features

01-tour-the-app/README.md

@@ -13,7 +13,9 @@ By the end of this chapter, you'll be able to:
 - Choose between a chat and a project session for a task
 - Explain the session modes: Interactive, Plan, and Autopilot
 - Select a model and reasoning effort based on task complexity
-- Optionally try voice dictation
+- Use prompt history to reuse and search previous prompts
+- Retry a response with a different model or reasoning effort
+- Try voice dictation (optional)
 
 > ⏱️ **Estimated Time**: ~30 minutes
 
@@ -177,6 +179,17 @@ You do not need a specific model for this course. Available models, effort level
 
 You can change the model and reasoning effort during a session without changing its mode.
 
+### Try Again with a Different Model
+
+If the agent's response doesn't work for you, you can retry it with a different model or reasoning effort without re-typing your prompt. Look for the **Retry** button that appears below a response in the conversation. Select it to retry with a different model, effort level, or context window. This is useful when the first attempt doesn't quite match your needs or when a higher reasoning effort might help with a tricky problem.
+
+## Prompts and Shortcuts
+
+You'll spend most of your time typing prompts in the composer box below the session. A few helpful shortcuts and features make prompt writing easier:
+
+- **Prompt history**: Press **Ctrl+R** (or **Cmd+R** on macOS) to see your recent prompts across all sessions. You can search through them and reuse a prompt by selecting it. This saves time when you run similar work regularly.
+- **Attach context**: Type `@` to attach files and folders, `#` to attach issues and pull requests, and `/` to run commands. Chapter 02 covers context in detail.
+
 ## Settings
 
 Select the gear icon at the bottom of the sidebar to open **Settings**. You do not need to change anything now, but it helps to know where each option lives.
@@ -206,9 +219,9 @@ The **Model providers** setting connects the app to additional providers. It doe
 <details>
 <summary>Optional: Voice dictation</summary>
 
-Voice dictation turns speech into editable prompt text, which can save time and effort when creating prompts.
+Voice dictation turns speech into editable prompt text, which can save time and effort when creating prompts. It is enabled by default, but you can customize your microphone settings and transcription model.
 
-Go back to the GitHub Copilot app's **Settings** dialog. Select **Voice dictation**, set up your input device and complete the configuration steps.
+Go back to the GitHub Copilot app's **Settings** dialog. Select **Voice dictation** to set up your input device and customize the configuration if needed.
 
 > **Note:** Microphone permission is granted at the operating-system level. Follow your operating system prompts to allow the GitHub Copilot app to use the microphone.
 

02-sessions-worktrees-context/README.md

@@ -11,6 +11,7 @@ By the end of this chapter, you'll be able to:
 - Start a worktree-backed session from a branch and attach an issue as context
 - Explain what a git worktree is and how it keeps each session's changes out of your `main` checkout
 - Add relevant context to a session so Copilot can understand the task and its supporting information
+- Use multiple ways to attach context: type `@` for files, `#` for issues, or drag and drop files from your computer
 - Decide between working in your current checkout, an isolated worktree, or a cloud sandbox
 - Use `/chronicle standup` and `/context` to review a session
 
@@ -84,6 +85,10 @@ The GitHub Copilot app lets you add context and commands in the prompt box with
 > [!TIP]
 > Provide the smallest amount of useful context. Less is often more.
 
+### Attaching Files
+
+In addition to typing `@` to reference files and folders, you can drag files from your computer and drop them directly onto a session or agent in the sidebar. This is useful when you have files ready to attach that aren't part of the repository. The dropped files are added to the session's context, and you can continue with your prompt.
+
 ### Slash Commands
 
 Slash commands are shortcuts you type in the prompt box. They can open app utilities, invoke agent behaviors, inspect usage, or trigger installed skills. The safest way to discover what your app supports is to type `/` in the prompt box and read the palette. Commands can vary by app version, enabled plugins, installed skills, and organization policy.

03-development-workflows/README.md

@@ -14,6 +14,7 @@ GitHub Copilot app connects both loops, but you remain responsible for reviewing
 By the end of this chapter, you'll be able to:
 
 - Use the review panel, tests, build output, and browser preview to validate a local change
+- Run code snippets directly from Copilot's responses using the Run button or copy and paste them into the terminal
 - Add a regression test and ask the rubber duck agent to critique your work
 - Use the **Issues** and **Pull requests** views to move from an issue to a pull request
 - Ask GitHub Copilot to address review comments and failing checks
@@ -107,6 +108,15 @@ The tests and build should pass before you introduce any changes. This gives you
 > [!NOTE]
 > Each practice branch opens in a separate worktree. Run `npm install` the first time you use a new worktree because dependencies aren't shared automatically.
 
+### Running Code Snippets in the Terminal
+
+When Copilot provides code snippets in a conversation, you have two ways to run them:
+
+1. **Copy and paste into the terminal** - Copy the code from Copilot's response and paste it into the Terminal tab in the review panel, just as you do above.
+2. **Run directly from the response** - Copilot's response may include a **Run** button next to Bash or PowerShell code snippets. Click it to execute the snippet directly in the session's terminal without copying and pasting. The terminal reuses the existing shell when available, so environment state and working directories carry over between runs.
+
+This direct execution is useful when you want to quickly validate a command without manually typing it, especially for longer or more complex snippets.
+
 ## Inner Loop: Develop and Validate on Your Machine
 
 The inner loop is: