Copilot - No token found but auth successful

[PerMalmberg]

Hi,

Moving to a new computer and using the exact same NeoVim config as on the old one but despite that I get the following when using CodeCompanion chat:

Copilot Adapter: No token found. Please refer to https://github.com/github/copilot.vim
   Error  13:51:41 notify.error CodeCompanion
[ERROR] 2026-05-25 13:51:41
Copilot Adapter: No token found. Please refer to https://github.com/github/copilot.vim
   Error  13:51:41 notify.error CodeCompanion
[ERROR] 2026-05-25 13:51:41
Failed to setup adapter

CoPilot auth says that I am authorized.

healthcheck codecompanion is all green.

I get the same error with minimal.lua though I had to add zbirenbaum/copilot.lua as a dependency for auth.

Any idea what could be causing this?

[cookesan]

CodeCompanion does not ask the Copilot plugin whether authentication succeeded; it looks for Copilot's token files on disk.

The adapter searches under the configured token parent for:

github-copilot/hosts.json
github-copilot/apps.json

So first check where those files are on the new machine:

ls ~/.config/github-copilot/hosts.json ~/.config/github-copilot/apps.json
echo "$XDG_CONFIG_HOME"

If your Copilot plugin stored them somewhere else, set the parent directory before CodeCompanion starts, for example:

let $CODECOMPANION_TOKEN_PATH = expand('~/.config')

Use the actual parent directory that contains github-copilot/. If the files do not exist, rerun Copilot auth in that same Neovim environment and restart Neovim after the token file is created.

[PerMalmberg]

This seems to be a copilot.lua issue, it is not writing either of those files, just a sqlite db.

[PerMalmberg]

Continuing here zbirenbaum/copilot.lua#706

[PerMalmberg]

@olimorris Seems apps.json isn't coming back and that tokens will be read from the sqlite db.
zbirenbaum/copilot.lua#706 (comment)

[PerMalmberg]

@olimorris I'd unmark this as answered if I could. Could you please?

copilot.lua was just released with the breaking change introduced by upstream changes. While we can pin it in the short term, it would be nice to retain the "it just works" experience we've had with CodeCompanion and copilot.lua.

https://github.com/zbirenbaum/copilot.lua/releases/tag/v3.0.0

[olimorris]

If you're choosing to put the token on disk with copilot.lua, then I'm sure that their latest release breaks that. But what about Copilot CLI or copilot.vim?

[PerMalmberg]

I don't use either, but copilot.vim has the same issue; github/copilot.vim#284 (comment)

[olimorris]

#3155 has added support for tokens via the SQLite database. The Copilot adapter has caching built in so this should be relatively performant.

@PerMalmberg would appreciate you testing this on your machine. I've confirmed it working on mine but the current hierarchy in the Copilot adapter is to search for the token in the JSON files and then fallback to the SQLite db. I'm not sure if that's the correct logic.

[PerMalmberg]

@olimorris I will. Right now I'm getting timeouts from CoPilot, I'll try again later.

[olimorris]

You'll get an immediate error if it can't find the token. A timeout is slightly more worrying.

[PerMalmberg]

Seems to be working fine now :) Thanks for the work that you do!