Repository navigation
/rubber-duck command not working in Copilot CLI #46225
Description
Activity
@ashis-baral Thanks for opening an issue. I'm going to transfer this internally.
As a general rule, if your package includes GitHub Support, that's a better path for resolving issues like this, in case there's a configuration issue. Or alternatively, you can open a discussion under https://github.com/orgs/community/discussions if not.
As we're unable to provide support in this repo, I won't be able to follow up here, but you'll see the text change if that's the needed outcome. Thanks again
Thank you for opening this issue! Updates to this documentation must be made internally. I have copied your issue to an internal issue, so I will close this issue.
@subatoi Thanks for clarifying. I’m not looking for support or troubleshooting here. I’m on the GitHub Free plan.
My intention was simply to report the documentation issue. If the /rubber-duck command is no longer supported, I can open a PR to remove or update the incorrect documentation.
Thanks for transferring the issue internally!
On looking into this it seems that there is a bug with how the CLI handles this command with some models. The error message is misleading and there's a caching issue that means you have to start a new session with a different model to be able to use
/rubber-duckas normal. For most models this works as documented.I've raised a dev issue and we'll look at updating the docs if it turns out some models do not support this command. Thanks for raising this.
Reacted by Ashis Kumar Baral
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/copilot/concepts/agents/copilot-cli/rubber-duck#manually-invoking-the-rubber-duck-agent
What part(s) of the article would you like to see updated?
The article states that the Rubber Duck agent can be manually invoked with the slash command:
However, when I run this command in the latest version of GitHub Copilot CLI, it returns:
The Rubber Duck agent itself is available and working correctly. For example, the following natural-language request works successfully in the same environment:
This suggests that the issue is specifically with the documented /rubber-duck slash-command invocation rather than the Rubber Duck agent itself.
Update the documentation if the /rubber-duck slash command is no longer supported.
Additional information
The issue does not appear to be that the Rubber Duck agent is unavailable, since the natural-language invocation successfully triggers it in the same environment.