Use the old Copilot CLI syntax in the new gh version

[NullDev]

Select Topic Area

Question

Body

I still had the old github-copilot-cli v0.1.21 installed where I could just do e.g. ?? list all files.
This doesn't work anymore (ERR_BAD_REQUEST) so I wanted to switch to the official gh cli that apparently has the copilot cli now.

I uninstalled the old one with npm rm -g @githubnext/github-copilot-cli and installed gh as per the docs.

Now, for the old one I still had aliases in my .bashrc / .zshrc:

eval "$(github-copilot-cli alias -- "$0")"

So I could do ?? query.

Is there any official way to get the old syntax back without limiting any new features?

Always typing gh copilot suggest "foo" seems really verbose and I really liked the intuitive syntax with ??.

[johanrosenkilde]

You may add the following aliases into your .bashrc or .zshrc:

alias '??'='gh copilot suggest -t shell'
alias 'git?'='gh copilot suggest -t git'
alias 'explain'='gh copilot explain'

This allows calling e.g. ?? list all files like with the Next technical preview Copilot CLI. The difference is that you still "accept" by getting the command into your clipboard, at which point you should exit the cli and paste in the command in the shell.

In an upcoming version of the gh version, it will be born with a feature more closely matching the Next technical preview's in terms of aliases for quick execution.

[NullDev]

Awesome, thanks!

[solrevdev]

Yeah thanks for the info 🙏

[huyz]

Don't forget ;)

alias 'gh?'='gh copilot suggest -t gh'

[rsmets]

I'm curious which new version the gh cli has copilot support? I can not find mention of it anywhere in the docs.

I'd love to upgrade because my old @githubnext/github-copilot-cli cli setup is no longer working - always throwing 404s (even after upgrading and re-authing). https://github.com/orgs/community/discussions/80191#discussioncomment-8081884

[rsmets]

Ah found the install instructions for the copilot cli extension 👍🏼

[johanrosenkilde]

The Next GitHub Copilot CLI technical preview is up and running again!

It was an unfortunate oversight when we sunset a few other previews in December that our Copilot CLI also stopped working. We will sunset our Copilot CLI technical preview in the not too far future, once the gh cli extension matures sufficiently.

[marcelosalloum]

It started working for me again after I updated the copilot package:

yarn global add @githubnext/github-copilot-cli

Maybe they messed up with the old DNS address?

[NullDev]

Apparently they fixed it 11 hours ago
#86354 (comment)