mirror of
https://github.com/github/awesome-copilot.git
synced 2026-09-20 21:34:45 +00:00
Document CLI v1.0.85/86 and VS Code 1.138 Copilot updates
Add coverage for recent GitHub Copilot CLI and VS Code changes to the Learning Hub: - Copilot CLI v1.0.85: transcriptView "concise" grouping, opt-in context management tools for agents/subagents, sandbox bypass session opt-out - Copilot CLI v1.0.86: include-custom-instructions agent frontmatter field for opting into repository instruction files (AGENTS.md, copilot-instructions.md, CLAUDE.md) - VS Code 1.138: Dev Container agent sessions, PR creation from Agent Host sessions, and automatic session cleanup (Mark as Done) Sources: - https://github.com/github/copilot-cli/blob/main/changelog.md - https://github.com/github/copilot-cli/releases - https://github.com/microsoft/vscode-docs/blob/main/release-notes/v1_138.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
co-authored by
Copilot
parent
0a66795706
commit
9677a3033f
@@ -3,7 +3,7 @@ title: 'Agents and Subagents'
|
||||
description: 'Learn how delegated subagents differ from primary agents, when to use them, and how to launch them in VS Code and Copilot CLI.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-09-12
|
||||
lastUpdated: 2026-09-17
|
||||
estimatedReadingTime: '9 minutes'
|
||||
tags:
|
||||
- agents
|
||||
@@ -202,6 +202,12 @@ This pairs with **improved workspace resolution**: agents can resolve a workspac
|
||||
|
||||
**Shareable session links** *(VS Code 1.138+)*: Agent Host sessions and chats now provide browser-addressable links, so you can reopen or share a specific Agents window session directly from another app, a GitHub issue, or terminal output — useful when handing off a delegated subagent's work to a teammate for review. You can also start a new session beside the current one in one step, keeping the current work visible while a second session starts.
|
||||
|
||||
**Run agent sessions in a local Dev Container** *(VS Code 1.138+, experimental)*: Enable `chat.agentHost.devContainer.enabled` to run an Agent Host session inside a local folder's Dev Container instead of on your host machine. The agent then uses the project's own toolchain and dependencies — useful when a subagent's work (like running tests or a build) depends on a specific environment that differs from your local setup. Docker must be installed.
|
||||
|
||||
**Create pull requests directly from agent sessions** *(VS Code 1.138+)*: The Agents window can generate a pull request title and description from a session's changes, let you review and edit them, choose draft status, and open the PR — without leaving the Agents window. This is useful once a subagent's delegated work is ready to hand off for review.
|
||||
|
||||
**Keep completed sessions organized** *(VS Code 1.138+, preview)*: Enable `chat.agentSessions.archiveNudge.enabled` to get a suggestion to mark a session as done once all its pull requests have merged, and optionally configure automatic cleanup (`chat.agentSessions.autoMarkAsDoneMergedSessionsAfterDays`, `chat.agentSessions.autoDeleteArchivedMergedSessionsAfterDays`) so finished delegated-work sessions don't pile up in your sessions list.
|
||||
|
||||
## Common questions
|
||||
|
||||
**Do users always invoke subagents directly?**
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 'Building Custom Agents'
|
||||
description: 'Learn how to create specialized GitHub Copilot agents with custom personas, tool integrations, and domain expertise.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-09-05
|
||||
lastUpdated: 2026-09-17
|
||||
estimatedReadingTime: '10 minutes'
|
||||
tags:
|
||||
- agents
|
||||
@@ -108,6 +108,17 @@ tools: ['codebase', 'terminal', 'github']
|
||||
|
||||
For MCP server tools, reference them by server name (e.g., `postgres`, `docker`). See [Understanding MCP Servers](../understanding-mcp-servers/) for details.
|
||||
|
||||
**include-custom-instructions** *(Copilot CLI v1.0.86+)*: By default, a custom agent's own instructions take the place of repository-level instruction files. Set `include-custom-instructions: true` to also load `AGENTS.md`, `copilot-instructions.md`, or `CLAUDE.md` alongside the agent's frontmatter instructions — useful when you want an agent to layer its specialized persona on top of your team's shared coding standards rather than replacing them entirely:
|
||||
|
||||
```yaml
|
||||
---
|
||||
name: 'Security Reviewer'
|
||||
description: 'Expert security auditor that reviews code for OWASP vulnerabilities'
|
||||
include-custom-instructions: true
|
||||
tools: ['codebase', 'terminal', 'github']
|
||||
---
|
||||
```
|
||||
|
||||
### Agent Instructions
|
||||
|
||||
After the frontmatter, write Markdown instructions that define the agent's behavior. Structure these clearly:
|
||||
|
||||
@@ -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-09-12
|
||||
lastUpdated: 2026-09-17
|
||||
estimatedReadingTime: '10 minutes'
|
||||
tags:
|
||||
- configuration
|
||||
@@ -946,6 +946,33 @@ copilot skill enable my-skill # enable a specific skill
|
||||
|
||||
*(v1.0.84+)* Command-line parsing moved from Commander to a Rust-based grammar that mirrors what the CLI actually parses, which also generates shell completions directly from that grammar — so `copilot <TAB>` now offers root flags alongside subcommands, and each subcommand only shows its own options. As a result of this change, some error and help wording changed, `copilot login --host` now works correctly, and `--max-autopilot-continues` no longer accepts scientific notation as a value.
|
||||
|
||||
### Concise Transcript View
|
||||
|
||||
*(v1.0.85+)* Set `transcriptView` to `"concise"` in `/settings` to group tool activity into expandable work summaries instead of showing every tool call inline. This keeps the timeline scannable during long sessions with heavy tool use — expand a summary only when you need to inspect the individual steps behind it.
|
||||
|
||||
### Opting In to Context Management Tools for Subagents
|
||||
|
||||
*(v1.0.85+)* New `/settings` options let you opt subagents (and the main agent) into **context management tools** — capabilities that let an agent actively manage its own context window (for example, summarizing or trimming stale history) rather than relying solely on automatic compaction. This is useful for long-running orchestrated workflows where subagents accumulate a lot of intermediate context. See [Agents and Subagents](../agents-and-subagents/) for more on how delegated work affects context usage.
|
||||
|
||||
### Sandbox Session Opt-Out from an Approved Bypass
|
||||
|
||||
*(v1.0.85+)* Managed sandbox sessions can now be disabled for the rest of the session directly from an approved sandbox bypass prompt, instead of having to separately run `/sandbox disable` afterward.
|
||||
|
||||
### Custom Agents Can Opt Into Repository Instruction Files
|
||||
|
||||
*(v1.0.86+)* Custom agents can set `include-custom-instructions: true` in their frontmatter to opt into repository instruction files (`AGENTS.md`, `copilot-instructions.md`, `CLAUDE.md`) that would otherwise be skipped in favor of the agent's own instructions:
|
||||
|
||||
```yaml
|
||||
---
|
||||
name: 'Security Reviewer'
|
||||
description: 'Expert security auditor'
|
||||
include-custom-instructions: true
|
||||
tools: ['codebase', 'terminal']
|
||||
---
|
||||
```
|
||||
|
||||
See [Building Custom Agents](../building-custom-agents/) for more on agent frontmatter fields.
|
||||
|
||||
## Common Questions
|
||||
|
||||
**Q: How do I disable Copilot for specific files?**
|
||||
|
||||
Reference in New Issue
Block a user