Skip to main content

Copilot CLI OpenCode

From GitHub Copilot CLI to OpenCode: A Pragmatic Take from a Pro+ User

I’m a GitHub Copilot Pro+ subscriber, and I’ll start with this: I genuinely love the GitHub ecosystem.

GitHub has shaped the way many of us work—code hosting, CI, issues, pull requests, and now AI-assisted development. Naturally, when GitHub released Copilot CLI, I decided to go all in.

Betting on Copilot CLI as an Exclusive Coding Agent

Despite its early preview status, I made a deliberate choice: Copilot CLI would be my exclusive coding agent.

I wanted a CLI-first, first-party AI experience, tightly integrated with GitHub. I knowingly accepted the risks that come with preview software. Initially, the bet paid off.

Contributing Back: When Feedback Turns into Features

Early on, I proposed a small but important enhancement: a command to list available models.

Issue: https://github.com/github/copilot-cli/issues/47

To my surprise (and appreciation), the idea was welcomed, discussed, and implemented. Huge thanks to the Copilot CLI team for that—this is exactly the kind of feedback loop developers value.

Encouraged by this success, I pushed the idea further.

The “Full Throttle Mode” Idea

My main friction with Copilot CLI was its strict behavior: one prompt = one model query.

For exploratory coding, refactoring, or deep problem-solving, this is unnecessarily limiting. So I proposed a kind of “full throttle mode”, allowing the agent to iterate, chain prompts, and consume requests when the user explicitly wants it.

Issue: https://github.com/github/copilot-cli/issues/915

The idea was triaged, but eventually stalled. That’s product reality—but the need didn’t disappear.

When Preview Software Bites Back

Then came a more concrete issue: I was suddenly unable to list models at all.

Issue: https://github.com/github/copilot-cli/issues/1081

Using preview software means accepting breakages—that part is on me. What’s more frustrating is the absence of response: no workaround, no acknowledgment, no direction.

At that point, I started looking for alternatives.

Rediscovering OpenCode (and a Key GitHub Announcement)

I remembered hearing about OpenCode, and then recalled a crucial announcement from GitHub:

GitHub Copilot now supports OpenCode

That announcement changed everything.

OpenCode: Exactly the Behavior I Was Looking For

Very quickly, one thing became obvious: OpenCode behaves exactly like the “full throttle mode” I had been asking for.

In my usual workflow:

  • I expect to naturally consume arround 80% of the 3000 included premium requests
  • I intentionally keep 20% in reserve for hard or critical problems

This is exactly how I want to work

On top of that:

  • Model listing works reliably
  • The behavior just what I want

My Advice

To the GitHub Team

Join OpenCode and consolidate it.

OpenCode already solves real problems Copilot CLI users are expressing. There is a clear opportunity here to align efforts instead of fragmenting them.

To GitHub Copilot CLI Users

Try OpenCode.

  • Pro+ users will likely love the flexibility
  • Free or basic Pro users should be mindful of premium request limits

Closing Thoughts

This isn’t a rant. It’s a field report from a paying, engaged user who wants GitHub’s AI tooling to succeed.

Copilot CLI has strong ideas and real potential. Today, OpenCode delivers the experience I was actively trying to achieve.

As developers, we optimize for flow, OpenCode gives me that flow.

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...
Read more

wget maven ntlm proxy

How to make wget, curl and Maven download behind an NTLM Proxy Working on CentOS, behind an NTLM proxy: yum can deal without problem with a NTLM Proxy wget, curl and Maven cannot The solution is to use " cntlm ". " cntlm " is a NTLM client for proxies requiring NTLM authentication. How it works Install "cntlm" Configure "cntlm"  by giving it your credentials by giving it the NTLM Proxy Start "cntlm" deamon (it listens to "127.0.0.1:3128") Configure wget, curl and Maven to use "cntlm" instead of using directly the NTLM Proxy Note: You will have then a kind of 2 stages Proxy : cntlm + the NTLM proxy Configure CNTLM After installing cntlm, the configuration file is in "cntlm.conf". You must have your domain (in the Windows meaning), proxy login and  proxy password. Mine are respectively: rktmb.org, mihamina, 1234abcd (yes, just for the example) You must have you NTLM Proxy Hostnama or IP ...
Read more

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...
Read more