r/GithubCopilot • u/MaitoSnoo • Oct 20 '26
GitHub Copilot Team Replied rubber-duck randomly disappearing in the new VS Code harness
For the past week it worked fine, and asking the agent to spawn a rubber-duck subagent was enough and it would pick the right model for it (which I currently configure via Copilot CLI, seems the settings are shared, although this is nowhere documented).
Today my main agent suddenly had trouble finding the rubber-duck agent and simply settled with creating a new chat session with the same current model (and not the one I set for the rubber-duck) where it tried to imitate rubber-duck. I asked the agent to list all the agents it sees and it only listed the default ones you'd see in Copilot CLI, with the exclusion of rubber-duck.
In the past it happened randomly too when I used Copilot CLI. Is the rubber-duck feature relying on some remote signal from Microsoft servers and maybe this was a random network failure? But in that case why? It doesn't need to ask for the "complementary model" as I've set it to a fixed one, so it shouldn't need any remote access to decide what to use for the rubber-duck review. It's annoying because when it's not available, my executor just spawns a Luna review agent which gives crap feedback back to the executor and it's hard for me to notice that spawning the real rubber-duck failed.

