From cfcf339c1f650fa80a637ff4a0b94857e12e27e6 Mon Sep 17 00:00:00 2001 From: Caleb Wilson Date: Tue, 9 Jun 2026 12:10:00 +0100 Subject: [PATCH] feat: add /ask command to Lesson 18 (Session Management) Addresses issue #67 by documenting the new /ask slash command introduced in v1.0.27. - Added /ask section after /usage in the concepts area - Added /ask hint to the Hints section - Explains that /ask allows ephemeral questions without polluting session history The /env and /statusline commands were also reviewed but deemed less central to the tutorial's learning flow, so they were not added. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- tutorial/lessons/18-session-management.md | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/tutorial/lessons/18-session-management.md b/tutorial/lessons/18-session-management.md index 2fbe640..2ebcc4a 100644 --- a/tutorial/lessons/18-session-management.md +++ b/tutorial/lessons/18-session-management.md @@ -47,6 +47,20 @@ This shows request counts, token usage, and other session metrics. --- +### Quick ephemeral questions + +**`/ask`** — Ask a one-off question without affecting your conversation history: + +``` +/ask What's the difference between Promise.all and Promise.allSettled? +``` + +This is useful when you need a quick lookup mid-task — checking syntax, verifying a concept, or confirming a command — without cluttering your main conversation context. The response appears immediately, but neither your question nor the answer enters the session history. Your next message continues from where you were before `/ask`. + +Think of it as a side channel for throwaway questions that would otherwise pollute your working context. + +--- + ### Running shell commands with `!` You can run a shell command directly from within your Copilot session using the `!` prefix: @@ -108,8 +122,9 @@ Sometimes it's better to start over than to correct course: 1. `--continue` resumes the most recent session; `/resume` lets you pick from all past sessions 2. Session IDs let you target a specific session — useful when you have several active workstreams 3. `/usage` gives you raw session stats — a quick health check before diving in -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, `/restart` when the CLI misbehaves, and `/resume` to pick up where you left off +4. `/ask` is perfect for quick throwaway questions — checking syntax or concepts without polluting your working context +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, `/restart` when the CLI misbehaves, and `/resume` to pick up where you left off ---