Skip to content

feat: add /ask command to Session Management lesson #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
calebwilson706 merged 1 commit into from
Jun 25, 2026
Merged

feat: add /ask command to Session Management lesson #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 17 additions & 2 deletions tutorial/lessons/18-session-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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

---

Expand Down