How to Migrate From GitHub Copilot to Verboo Code

Short answer: migrating from GitHub Copilot to Verboo Code changes the limit, not the workflow. The monthly AI Credits pool that drains fast under heavy agent use is replaced by unlimited tokens at a fixed price. You can keep Copilot exactly as it is and just swap the engine behind it via BYOK, or move straight to the Verboo Code terminal. Either migration takes under 5 minutes.

What decides the switch

Attribute	GitHub Copilot	Verboo Code
Usage limit	Per-token AI Credits pool (chat, agent, PR review); code completion stays unlimited	Unlimited tokens
Price	Free · Pro US$ 10/mo · Pro+ US$ 39/mo · Max US$ 100/mo	From R$ 99/month, fixed price
Models	GPT-5.6, Claude Sonnet 5, Gemini 3.1 and others, picked in the selector	11 open models (GLM-5.2, DeepSeek V4, Kimi K2.7, and more)
Where it runs	IDE extension, app, and its own CLI	Terminal CLI, dedicated GPU in Brazil

How to migrate

Two paths, pick the one that fits your setup.

Option 1: keep Copilot, swap only the engine

For anyone who doesn't want to give up the extension or Copilot's inline autocomplete. Only chat and agent mode switch to running on Verboo Code.

export COPILOT_PROVIDER_BASE_URL=https://code.verboo.ai/router/v1
export COPILOT_PROVIDER_TYPE=openai
export COPILOT_PROVIDER_API_KEY=vbk_your_key_here
export COPILOT_MODEL=glm-5.2

copilot

In the app and the VS Code extension, the path is through the UI: generate a key at code.verboo.ai/api-keys (it's shown once, copy it right away), open Settings → Model Providers → Add Provider → OpenAI Compatible, paste the base URL https://code.verboo.ai/router/v1 and the key. The model you pick shows up in Copilot's model picker, next to the GitHub-hosted ones.

Option 2: leave Copilot, move to the Verboo Code terminal

npm install -g @verboo/code
verboo

The verboo command opens your browser to finish OAuth login at code.verboo.ai the first time. After that, just run verboo to open the session. To log in again on another machine: verboo /login.

When to stay where you are

Don't migrate if your case is one of these:

You rarely run out of Copilot's AI Credits pool, and your current plan covers you without surprises.
You depend on Copilot's inline autocomplete daily and don't even want to test another flow (in that case, use Option 1 above, no need to give up anything).
Your whole team already standardized on Copilot inside GitHub, and switching tools costs more than solving the credit ceiling.

Questions from people migrating

Do I lose my Copilot history?

No, if you use Option 1: the extension, your code, and Copilot's chat history stay intact, only the model behind chat and agent mode changes. With Option 2, your Git code doesn't change at all (it's the same repository), but Copilot's chat history stays in Copilot, it doesn't carry over to the terminal.

Can I use both at the same time?

Yes, and it's the most common setup. Enable Option 1 in Copilot for day-to-day work, with PR review and GitHub integration, and keep the Verboo Code CLI open in parallel for the longer task, with no token cap.

What if I already paid for this month of Copilot?

No need to cancel to try it out. Both run side by side, and you decide which one to keep only after seeing how it behaves with your real usage.

If what's blocking your task is Copilot's credit running out mid-way, not the model itself, Verboo Code fixes that with unlimited tokens at a fixed price, inside Copilot or in the terminal.

Still deciding? Read the full analysis between GitHub Copilot and Verboo Code, with benchmarks and a comparison table.