mirror of
https://github.com/github/awesome-copilot.git
synced 2026-04-30 12:15:56 +00:00
Update Learning Hub for Copilot CLI v1.0.35–v1.0.37 changes (#1546)
- copilot-configuration-basics.md: - Add continueOnAutoMode config setting (v1.0.35) - Document --name/--resume=<name> for named sessions (v1.0.35) - Add /session delete, delete <id>, delete-all subcommands (v1.0.35) - Add session picker sort order (press 's', v1.0.37) - Update /ask to note markdown rendering including tables (v1.0.37) - Update /statusline to mention 'changes' line-count toggle (v1.0.36) - Add /keep-alive command (now available without experimental mode, v1.0.36) - using-copilot-coding-agent.md: - Document /remote on and /remote off subcommands and status display (v1.0.36) - automating-with-hooks.md: - Add note on location-based permission persistence enabled by default (v1.0.37) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
6446c1aa62
commit
8c214f2506
@@ -3,7 +3,7 @@ title: 'Automating with Hooks'
|
||||
description: 'Learn how to use hooks to automate lifecycle events like formatting, linting, and governance checks during Copilot agent sessions.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-04-27
|
||||
lastUpdated: 2026-04-28
|
||||
estimatedReadingTime: '8 minutes'
|
||||
tags:
|
||||
- hooks
|
||||
@@ -239,6 +239,8 @@ automatically before the agent commits changes.
|
||||
|
||||
The `PermissionRequest` hook fires when the CLI shows a permission prompt to the user — for example, when the agent wants to run a shell command for the first time. Unlike `preToolUse` (which can block specific tool *calls*), `PermissionRequest` intercepts the permission approval UI itself, making it ideal for **headless and CI environments** where no one is available to click "Allow".
|
||||
|
||||
> **Location-based persistence (v1.0.37+)**: Permission approvals are now persisted by directory by default — once you approve a permission for a given working directory, that approval carries over to future sessions started in the same directory. You no longer need to re-approve the same tools every time. Use `PermissionRequest` hooks to automate approvals in CI, and rely on the persisted approvals for interactive local sessions.
|
||||
|
||||
When your hook script exits with code `0`, the permission request is **approved**. Exit with a non-zero code to **deny** it (the user will still see the prompt).
|
||||
|
||||
```json
|
||||
|
||||
@@ -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-04-16
|
||||
lastUpdated: 2026-04-28
|
||||
estimatedReadingTime: '10 minutes'
|
||||
tags:
|
||||
- configuration
|
||||
@@ -391,6 +391,7 @@ CLI settings use **camelCase** naming. Key settings added in recent releases:
|
||||
| `statusLine` | Show status line in the terminal UI |
|
||||
| `include_gitignored` | Include gitignored files in `@` file search |
|
||||
| `extension_mode` | Control extensibility (agent tools and plugins) |
|
||||
| `continueOnAutoMode` | Automatically switch to the auto model on rate limit instead of pausing |
|
||||
|
||||
> **Note**: Older snake_case names (e.g., `include_gitignored`, `auto_updates_channel`) are still accepted for backward compatibility, but camelCase is now the preferred format.
|
||||
|
||||
@@ -425,6 +426,25 @@ The `/session rename` command renames the current session. When called **without
|
||||
|
||||
Auto-generated names help you find sessions quickly when switching between multiple backgrounded sessions.
|
||||
|
||||
You can also name a session at startup with the `--name` flag, and resume it by name later:
|
||||
|
||||
```bash
|
||||
copilot --name "auth-refactor" # start a session with a given name
|
||||
copilot --resume="auth-refactor" # resume that session by name
|
||||
```
|
||||
|
||||
The `/session delete` command removes sessions you no longer need:
|
||||
|
||||
```
|
||||
/session delete # delete the current session
|
||||
/session delete <id> # delete a session by ID
|
||||
/session delete-all # delete all sessions
|
||||
```
|
||||
|
||||
You can also press **x** on a highlighted session in the session picker (`--resume`) to delete it directly from the list.
|
||||
|
||||
In the session picker, press **`s`** to cycle the sort order: relevance, last used, created, or name. The picker also shows the branch name and idle/in-use status for each session.
|
||||
|
||||
The `/rewind` command opens a timeline picker that lets you roll back the conversation to any earlier point in history, reverting both the conversation and any file changes made after that point. You can also trigger it by pressing **double-Esc**:
|
||||
|
||||
```
|
||||
@@ -459,7 +479,7 @@ The exported file contains everything needed to view the session without a netwo
|
||||
|
||||
**Keyboard shortcuts for queuing messages**: Use **Ctrl+Q** or **Ctrl+Enter** to queue a message (send it while the agent is still working). **Ctrl+D** no longer queues messages — it now has its default terminal behavior. If you have muscle memory for Ctrl+D queuing, switch to Ctrl+Q.
|
||||
|
||||
The `/ask` command lets you ask a quick question without affecting your conversation history. The current session context is preserved, so you can use it for one-off lookups without derailing an ongoing task:
|
||||
The `/ask` command lets you ask a quick question without affecting your conversation history. The current session context is preserved, so you can use it for one-off lookups without derailing an ongoing task. Responses are rendered as full markdown, including tables and formatted links:
|
||||
|
||||
```
|
||||
/ask What does the `retry` utility in src/utils do?
|
||||
@@ -471,12 +491,20 @@ The `/env` command shows all loaded environment details — instructions, MCP se
|
||||
/env
|
||||
```
|
||||
|
||||
The `/statusline` command (with `/footer` as an alias) lets you control which items appear in the terminal status bar. You can show or hide individual indicators like the working directory, current branch, effort level, context window usage, and quota:
|
||||
The `/statusline` command (with `/footer` as an alias) lets you control which items appear in the terminal status bar. You can show or hide individual indicators like the working directory, current branch, effort level, context window usage, and quota. The **changes** toggle shows a running count of added/removed lines for the session — useful when tracking the scope of an ongoing edit:
|
||||
|
||||
```
|
||||
/statusline # show the statusline configuration menu
|
||||
```
|
||||
|
||||
The `/keep-alive` command prevents the system from sleeping while Copilot CLI is active. This is useful during long-running agent sessions on laptops or machines with aggressive sleep settings:
|
||||
|
||||
```
|
||||
/keep-alive # toggle keep-alive on or off
|
||||
```
|
||||
|
||||
> **Note**: `/keep-alive` was previously an experimental feature. As of v1.0.36, it is available without enabling experimental mode.
|
||||
|
||||
The `/allow-all` command (also accessible as `/yolo`) enables autopilot mode, where the agent runs all tools without asking for confirmation. It now supports `on`, `off`, and `show` subcommands:
|
||||
|
||||
```
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 'Using the Copilot Coding Agent'
|
||||
description: 'Learn how to use GitHub Copilot coding agent to autonomously work on issues, generate pull requests, and automate development tasks.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-04-16
|
||||
lastUpdated: 2026-04-28
|
||||
estimatedReadingTime: '12 minutes'
|
||||
tags:
|
||||
- coding-agent
|
||||
@@ -346,10 +346,12 @@ Launch a session that registers with GitHub for remote access:
|
||||
copilot --remote
|
||||
```
|
||||
|
||||
Or open a remote control tab from inside an existing session:
|
||||
Or open a remote control tab from inside an existing session, and check or toggle its state:
|
||||
|
||||
```
|
||||
/remote
|
||||
/remote # show current remote control status
|
||||
/remote on # enable remote control and register with GitHub
|
||||
/remote off # disable remote control for this session
|
||||
```
|
||||
|
||||
The **Remote** tab in the CLI shows all active coding agent tasks from the repository. Select a task to connect and begin sending steering messages.
|
||||
|
||||
Reference in New Issue
Block a user