AIToday
AI Coding AssistantsLarge Language ModelsPublickeyPublished: Sep 2, 2026, 01:01 JST2 min read

VS Code's 'Rubber Duck' feature lets developers get a second AI opinion

VS Code's 'Rubber Duck' feature lets developers get a second AI opinion

Key takeaway

  • VS Code now offers an experimental feature called 'Rubber Duck' that lets developers request a second opinion from a different AI agent.

  • This helps catch mistakes that a single AI's self-review might miss.

  • It was previously in GitHub Copilot CLI and is now in VS Code.

3 Key Points

  1. What happened

    Visual Studio Code 1.135 now includes an experimental 'Rubber Duck' feature that lets developers request a second opinion from a different AI agent, separate from the main coding assistant. It was first introduced in GitHub Copilot CLI in April 2026 and has now been adapted for VS Code.

  2. Why it matters

    The feature addresses a key limitation of AI-assisted development: when a single AI model reviews its own work, it tends to use the same biases and may miss errors. By using a different AI model for review, developers can catch mistakes earlier, reducing the need to redo planning or coding—saving time and effort.

  3. What to watch

    The feature is available via the '/rubber-duck' command in the Copilot Agent Host session within VS Code. It is part of a series of updates in VS Code 1.132 to 1.135, which also include a hybrid Markdown editor, a comment feature for web pages in the integrated browser, and automatic hot reload for local HTML files.

Ask the AI about this article →

Context & Analysis

The introduction of the Rubber Duck feature in VS Code comes from a practical need: AI agents often fall into the trap of self-review bias. When the same AI model plans and reviews its own implementation, it may overlook errors due to inherent biases. By tapping a separate AI agent for a second opinion, developers can increase the chances of catching problems early, saving time and reducing the rework that often follows late-stage failures. The feature's name is a nod to a classic debugging technique where programmers explain their code to a rubber duck to spot issues. This move is part of a broader trend in developer tools to improve AI reliability through multi-model collaboration. As these tools evolve, they may help reduce the trial-and-error that currently accompanies AI-assisted coding, though the effectiveness of cross-model reviews is still an area of active experimentation.

FAQ

How do I use the Rubber Duck feature in VS Code?
You can use it by typing the '/rubber-duck' command in the Copilot Agent Host session within VS Code.
What is the purpose of the Rubber Duck feature?
The purpose is to improve code review quality by getting a second opinion from a different AI model, which can help catch mistakes that might be missed if the same AI reviews its own work.
Was the Rubber Duck feature available before this?
Yes, it was first introduced as an experimental implementation in GitHub Copilot CLI in April 2026, and has now been implemented experimentally in VS Code with improved usability.

Get the latest AI Coding Assistants news every morning

For example, today's edition would include:

  • Claude Code to permanently raise usage limits by 25%Ben's Bites · 1h ago
  • OpenClaw 2.0 launches, targeting enterprise AI teamsVentureBeat AI · 13h ago
  • AI Coding Shifts from Prompts to Context to HarnessITmedia AI+ · 20h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleMiddle Managers Key to AI Adoption