VS Code 1.135 Gives AI Coding Agents a Second Opinion

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Anyone who has leaned on an AI coding agent for a few months knows the pattern. The agent writes confident code, the tests pass, and then a reviewer catches an edge case the agent never considered. The model isn’t lying to you. It just doesn’t know what it doesn’t know, and it has no one in the room to push back. Microsoft’s latest release of Visual Studio Code, version 1.135, takes a direct swing at that problem. The headline addition is an experimental feature called Rubber Duck, a nod to the old programmer’s trick of explaining your code out loud to a literal rubber duck to catch your own mistakes. VS Code’s version replaces the duck with a second AI model. Rubber Duck runs inside Copilot agent host sessions. Type /rubber-duck and a different model reviews the primary agent’s plans, code, and tests, looking specifically for gaps the first model may have missed. Microsoft describes it as a way to get “a second opinion from a complementary model on the agent’s work,” aimed at surfacing missed details and edge cases before they become production bugs. The idea behind putting two different models on the same task isn’t new. Engineering teams have used pair programming and code review for the same reason for decades: a second set of eyes, working from different assumptions, finds different mistakes. Rubber Duck applies that same logic to agentic AI, where a single model working alone can develop blind spots that are hard to catch from inside its own reasoning. The release doesn’t stop at Rubber Duck. VS Code 1.135 also introduces an Agent Host built on what Microsoft calls …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/vs-code-1-135-gives-ai-coding-agents-a-second-opinion/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.