Skip to content

[bot] Add VS Code 1.135 Copilot features to Learning Hub - #34

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
learning-hub/vs-code-1135-updates-37b546828353cc9b
Draft

github-actions[bot] wants to merge 1 commit into
mainfrom
learning-hub/vs-code-1135-updates-37b546828353cc9b

Conversation

@github-actions

Copy link
Copy Markdown

What was found

VS Code 1.135 (released 2026-08-26) shipped three notable GitHub Copilot improvements:

  1. Continue external agent sessions in VS Code — VS Code can now show agent sessions started in the Copilot app (or other external tools) and let you continue them inside the editor, controlled by the chat.agentSessions.showExternal setting.
  2. /rubber-duck command (Experimental) — A direct /rubber-duck slash command is now available in VS Code, providing a second opinion from a complementary model to catch missed details and edge cases.
  3. Detailed chat turn usage — Each chat turn now shows a per-model token breakdown (input, cached input, output), making it easy to understand context consumption across multi-model sessions.

What was updated

Page Change
github-copilot-app.md Added new "Continuing Copilot App Sessions in VS Code" section covering cross-surface session continuity and the chat.agentSessions.showExternal setting
agents-and-subagents.md Updated the rubber-duck agent section to document the new direct /rubber-duck VS Code command alongside the existing CLI path
understanding-copilot-context.md Added "Viewing per-turn token usage" subsection under Token Limits and Context Prioritization

All three pages had their lastUpdated date bumped to 2026-08-27.

Source

Generated by Learning Hub Updater · 95.7 AIC · ⌖ 7.74 AIC · ⊞ 5.8K · ◷

- Add cross-surface session continuity section to github-copilot-app.md
- Update rubber-duck agent section to document VS Code 1.135 /rubber-duck command
- Add per-turn token usage breakdown to understanding-copilot-context.md
- Bump lastUpdated dates to 2026-08-27

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants