Problems with Copilot Plugin in Neovim (nvim)

[Linux-Alex]

Select Topic Area

Bug

Body

Description:
The latest version of copilot.vim (GitHub repository, version 1.42.0) contains a critical bug. After successfully connecting to a GitHub account, the following error occurs:

Error detected while processing function copilot#Command[33]..function copilot#Command[25]..3:
line   50:
E121: Undefined variable: status
E116: Invalid arguments for function get
Copilot: unknown command 'setuo'
Error detected while processing function copilot#Command[33]..function copilot#Command[25]..3:
line   50:
E121: Undefined variable: status
E116: Invalid arguments for function get

This issue does not appear to be related to the Node.js version, as I was using Node.js v22.14.0 at the time.

Workaround:
I was able to resolve the issue by downgrading the plugin to an earlier version: 1.34.0 (May 2024). I did not test other versions, but I selected this one because it worked with my previous configuration.

Steps to Reproduce:

1. Install copilot.vim version 1.42.0 in Neovim.
2. Successfully authenticate with GitHub.
3. Run :Copilot setup or attempt to use Copilot.
4. Observe the error message.

Expected Behavior:
Copilot should initialize without errors and work as expected after authentication.

System Information:

• OS: Kubuntu 24.04.2 LTS
• Neovim Version: v0.9.5
• Node Version: 22.14.0
• Copilot.vim Version: 1.42.0

Additional Notes:

• The issue persists after reinstalling the plugin and clearing configuration files.
• Downgrading to 1.34.0 resolves the problem.
• Further investigation is needed to determine if intermediate versions are also affected.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[sitano]

Yes, it does not work.
This error is a mistake in the implementation of handling of Authentication failure at:

function! s:commands.setup(opts) abort
  let startup_error = copilot#Client().StartupError()
  if !empty(startup_error)
      echo 'Copilot: ' . startup_error
      return
  endif

  let data = copilot#Call('signIn', {})

  if has_key(data, 'verificationUri')
    ...
  elseif get(data, 'status', '') isnot# 'AlreadySignedIn'
    ...
  endif

  -- status is not defined if we did not enter if-clause.
  let user = get(status, 'user', '<unknown>')

  echo 'Copilot: Authenticated as GitHub user ' . user
endfunction

but anyway it should not happen.

In the log I see Copilot log some expired certificates:

[2025-02-26 11:20:12] [INFO] [lsp] GitHub Copilot Language Server 1.274.0 initialized
[2025-02-26 11:20:12] [WARN] [certificates] Failed to parse certificate # ACCVRAIZ1
 Error: error:0480006C:PEM routines::no start line
    at new X509Certificate (node:internal/crypto/x509:119:21)
    at /home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificateReaders.ts:79:36
    at Array.filter (<anonymous>)
    at Pfe.removeExpiredCertificates (/home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificateReaders.ts:77:32)
    at Pfe.getAllRootCAs (/home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificateReaders.ts:68:38)
    at F1e.createSecureContext (/home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificates.ts:47:23) {
  library: 'PEM routines',
  reason: 'no start line',
  code: 'ERR_OSSL_PEM_NO_START_LINE'
}
[2025-02-26 11:20:12] [WARN] [certificates] Failed to parse certificate # ACCVRAIZ1
 Error: error:0480006C:PEM routines::no start line
    at new X509Certificate (node:internal/crypto/x509:119:21)
    at /home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificateReaders.ts:79:36
    at Array.filter (<anonymous>)
    at Pfe.removeExpiredCertificates (/home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificateReaders.ts:77:32)
    at Pfe.getAllRootCAs (/home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificateReaders.ts:68:38)
    at F1e.createSecureContext (/home/sitano/.local/share/nvim/lazy/copilot.vim/lib/src/network/certificates.ts:47:23) {
  library: 'PEM routines',
  reason: 'no start line',
  code: 'ERR_OSSL_PEM_NO_START_LINE'
}
[2025-02-26 11:20:12] [INFO] [certificates] Removed 2 expired certificates

any ideas?

[sitano]

Solution: delete ~/.config/github-copilot created by other versions of the github copilot plugins in other IDEs (it will of course erase previously created copilot sessions and auth from app.json). Than restart nvim and do Copilot setup - worked for me.

[sitano]

@ThomasCode92 then I can suggest trying running :debug Copilot setup to trace step by step where it fails and with what error. For me it was auth via sessions created by something else. For commands take a look at :help debug. Use step and echo blah.

[ThomasCode92]

@sitano Thanks for your quick reply!
This is the output of the debug command

FYI, I checked Copilot in VS Code and there I'm still able to use Copilot, so I suppose there is nothing wrong with my account.

[HWZen]

Same probrom in Windows+vim.

I tried it but the problem remains.

Waitting for an available answer.

[ThomasCode92]

@HWZen, if I recall correctly, my problem was related to an auth error. I use an organization copilot subscription, so could not use the models from the marked place. Can you run :CopilotChatModels and select a non-github_models model?

Link to the discussion that solved my problem: CopilotC-Nvim/CopilotChat.nvim#1052

[HWZen]

@ThomasCode92 Unfortunately, Vim thow E492: CopilotChatModels is not a command.
I'm not using the copilot chat extra.

[SpaceShaman]

I managed to fix this on my setup.

In my case the problem was not my Copilot account, but another plugin interfering with the setup flow. I had github/copilot.vim and folke/sidekick.nvim enabled at the same time. With Sidekick enabled, :Copilot setup kept failing and I got the misleading “Please use :LspCopilotSignIn to sign in” message.

What worked for me:

1. Temporarily disable Sidekick (or any other plugin that hooks into
   Copilot/LSP status)
2. Start Neovim with only copilot.vim
3. Run :Copilot setup and complete sign-in
4. Re-enable Sidekick

After that, both plugins worked correctly again.

So if anyone hits this, check whether another plugin is intercepting or overriding the Copilot auth/setup flow.