fix: update tutorial lessons with Copilot CLI v1.0.40-v1.0.43 changes

Agent-Logs-Url: https://github.com/instil/github-copilot-tutorial/sessions/a7e38ee4-b042-45f3-b120-a688c0609276

Co-authored-by: calebwilson706 <71669491+calebwilson706@users.noreply.github.com>

Author: Copilot

tutorial/lessons/08-planning-mode.md

@@ -36,6 +36,12 @@ There are two ways:
 
 Look at the bottom of your terminal to see which mode you're in. Just keep pressing Shift+Tab until you see the plan mode indicator.
 
+> **Note on Autopilot Mode:** When using Autopilot Mode, Copilot limits itself to 5 continuation messages by default to prevent unbounded autonomous execution. You can adjust this limit with the `--max-autopilot-continues` flag when launching Copilot:
+> ```
+> copilot --max-autopilot-continues 10
+> ```
+> This safety default means Autopilot Mode will pause and wait for your input after 5 steps in a longer task.
+
 **`/plan` command** — You can also type `/plan` followed by your prompt:
 
 ```

tutorial/lessons/14-session-management.md

@@ -29,6 +29,18 @@ Each session has a unique ID. You can resume a specific session by ID:
 
 ---
 
+### Session history with `/chronicle`
+
+**`/chronicle`** — Review a structured history of your session, including which files were read or edited and when:
+
+```
+/chronicle
+```
+
+This shows a timeline of file interactions during your session — useful for understanding what Copilot accessed and in what order. It's especially helpful when you want to audit a long session or hand off context to a colleague.
+
+---
+
 ### Context compression
 
 As conversations grow, the context window fills up. Copilot handles this automatically — at 95% token capacity, it auto-compacts the conversation to make room. But you can also manage it manually:
@@ -115,20 +127,22 @@ Sometimes it's better to start over than to correct course:
 
 1. Try `/context` to see your token usage visualisation
 2. Try `/usage` to see your session statistics
-3. Think about when you'd use `--continue` vs `/resume`:
+3. Try `/chronicle` to see a timeline of files accessed in this session
+4. Think about when you'd use `--continue` vs `/resume`:
    - `--continue`: "I closed my terminal but want to pick up exactly where I left off"
    - `/resume`: "I have several ongoing sessions and want to choose which one to revisit"
-4. If your context feels long, try `/compact "Focus on the current lesson"`
+5. If your context feels long, try `/compact "Focus on the current lesson"`
 
 ---
 
 ## Hints
 
 1. `/context` shows a visual breakdown — it's the quickest way to understand your token budget
 2. `/usage` gives you raw session stats
-3. `/compact` is your friend for long sessions — it summarises without losing the thread
-4. `/restart` reloads the CLI without clearing your conversation — useful when the CLI feels buggy or after changing config
-5. This is about building habits: use `/clear` between tasks, `/compact` when sessions get long, `/restart` when the CLI misbehaves, and `/resume` to pick up where you left off
+3. `/chronicle` shows a timeline of files accessed in this session — useful for auditing what Copilot read or wrote
+4. `/compact` is your friend for long sessions — it summarises without losing the thread
+5. `/restart` reloads the CLI without clearing your conversation — useful when the CLI feels buggy or after changing config
+6. This is about building habits: use `/clear` between tasks, `/compact` when sessions get long, `/restart` when the CLI misbehaves, and `/resume` to pick up where you left off
 
 ---
 

tutorial/lessons/15-programmatic-mode.md

@@ -28,6 +28,20 @@ cat error.log | copilot -p "explain this error and suggest a fix" > summary.txt
 git diff main | copilot -p "review these changes for bugs"
 ```
 
+### Attaching files and images
+
+In non-interactive mode, use `--attachment` to pass images or documents alongside your prompt:
+
+```bash
+copilot -p "describe the UI shown in this screenshot" --attachment screenshot.png
+```
+
+```bash
+copilot -p "review the architecture described in this diagram" --attachment architecture.pdf
+```
+
+This enables CI/automation workflows that include visual content — for example, screenshot regression checks or automated design review pipelines. You can include multiple `--attachment` flags in a single command.
+
 ### Scoping permissions
 
 When running in automation, lock down what Copilot can do:

tutorial/lessons/16-model-selection.md

@@ -12,9 +12,11 @@ Copilot CLI supports multiple AI models, each with different strengths:
 
 | Model | Best for |
 |-------|----------|
-| **Claude Sonnet 4.6** (default) | Daily coding tasks, good balance of speed and quality |
-| **Claude Opus 4.6** | Complex reasoning, architectural work, thorough analysis |
-| **GPT-5** | Code generation, broad knowledge |
+| **Claude Opus 4.5** (default) | Complex reasoning, architectural work, thorough analysis |
+| **Claude Sonnet 4.5** | Daily coding tasks, good balance of speed and quality |
+| **GPT-5.2 Codex** | Code generation, broad knowledge |
+
+In addition to specific models, Copilot CLI offers an **Auto** mode that uses server-side model routing to automatically select the best model for each request in real time. This can give you better results without you having to manually switch models.
 
 ### Switching models
 
@@ -75,9 +77,10 @@ This creates a `.github/copilot-instructions.md` file with sensible defaults bas
 1. Try `/model` to see what models are available and how to switch between them
 2. Try `/theme` to see available visual themes
 3. Think about when you'd switch models:
-   - Working on a quick bug fix? Stay on Sonnet 4.6
-   - Designing a complex architecture? Switch to Opus 4.6
-   - Want a different perspective on an approach? Try GPT-5.3 Codex
+   - Working on a quick bug fix? Stay on Sonnet 4.5
+   - Designing a complex architecture? Switch to Opus 4.5
+   - Want a different perspective on an approach? Try GPT-5.2 Codex
+   - Not sure which model to use? Try **Auto** mode and let Copilot decide
 
 ## Hints
 

tutorial/lessons/18-working-with-images.md

@@ -13,6 +13,7 @@ How to use images with Copilot CLI — debugging from screenshots, implementing
 | **Drag and drop** | Drag an image file into the terminal | Quick one-off references |
 | **Paste** | `Ctrl+V` (or `Cmd+V` on Mac) | Screenshots you just captured |
 | **File path** | Reference the image path with `@` in your prompt | Images already in your project |
+| **`--attachment` flag** | `copilot -p "..." --attachment image.png` | CI/automation and non-interactive mode |
 
 ### Common use cases
 
@@ -48,7 +49,8 @@ Option C — Just read:
 
 1. The easiest approach: take a screenshot of this terminal right now (`Cmd+Shift+4` on Mac, `Win+Shift+S` on Windows), then paste it into Copilot and ask "what do you see?"
 2. Copilot can read most common image formats: PNG, JPG, GIF, WebP
-3. This is about knowing the capability exists — you'll use it naturally when you encounter a visual debugging situation
+3. For CI/automation scripts, use `--attachment` with the `-p` flag: `copilot -p "describe this" --attachment image.png`
+4. This is about knowing the capability exists — you'll use it naturally when you encounter a visual debugging situation
 
 ## Completion Criteria