Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-05-15 19:21:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update Learning Hub with CLI v1.0.42-1.0.43 features (#1648)

Browse Source 
- understanding-mcp-servers.md: add Troubleshooting section with MCP
  stderr diagnostics (v1.0.42+) and /mcp show usage guidance
- copilot-configuration-basics.md: document -C startup flag (v1.0.42+),
  Auto mode server-side model routing (v1.0.43+), and /statusline
  username toggle (v1.0.43+)
- agents-and-subagents.md: add rubber-duck agent experimental feature
  documentation (v1.0.42+)

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]
2026-05-08 12:26:48 +10:00
committed by GitHub
parent a4ca380b7c
commit 93acc6c6eb
3 changed files with 61 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/src/content/docs/learning-hub/agents-and-subagents.md
+16 -1
View File
@@ -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-05-04
lastUpdated: 2026-05-07
estimatedReadingTime: '9 minutes'
tags:
- agents
@@ -134,6 +134,21 @@ The important behavior is different from a single chat turn:
That makes `/fleet` a practical way to launch subagents even if you are not authoring custom agent files yourself.
### Rubber-duck agent (experimental)
Available in `/experimental` (v1.0.42+), the **rubber-duck agent** applies a novel multi-model pattern: when you're working in a GPT-powered session, the rubber-duck agent internally routes certain requests through Claude to provide a second perspective. The idea is similar to rubber-duck debugging — talking through a problem with a different "listener" often surfaces assumptions or blind spots you didn't notice.
To try it, enable experimental features and then select the rubber-duck agent from the agent picker:
```
/experimental # toggle experimental features
/agent # open the agent picker and select rubber-duck
```
Because it runs as a sub-agent layer rather than replacing your primary model, you keep your current session model and context while the rubber-duck analysis runs in the background.
> **Note**: This is an experimental feature and may change. Provide feedback via `/feedback` if you find it useful.
## Orchestration patterns that work well
### Coordinator and worker