Agent service not initialized

[karamanliev]

Hello, I get this error every time I attach to a buffer for the first time after entering neovim, then entering insert mode and starting to write immediately:

RPC[Error] code_name = ServerNotInitialized, message = "Agent service not initialized."

It's consistent and it happens 100% of the time. I'm pretty much using a default config:

  {
    'zbirenbaum/copilot.lua',
    enabled = true,
    cmd = 'Copilot',
    event = { 'InsertEnter' },
    config = function()
      local colors = require('tokyonight.colors').setup()
      vim.api.nvim_set_hl(0, 'CopilotSuggestion', { fg = colors.fg_dark })

      require('copilot').setup({
        panel = {
          enabled = true,
          keymap = {
            open = '<M-p>',
          },
        },
        suggestion = {
          enabled = true,
          auto_trigger = true,
          keymap = {
            accept = false,
            next = '<M-]>',
            prev = '<M-[>',
            dismiss = '<C-c>',
          },
        },
        filetypes = {
          yaml = false,
          markdown = false,
          help = false,
          gitcommit = false,
          gitrebase = false,
          hgcommit = false,
          svn = false,
          cvs = false,
          ['.'] = false,
        },
      })

      -- Enable <Tab> to indent if no suggestions are available
      vim.keymap.set('i', '<Tab>', function()
        if require('copilot.suggestion').is_visible() then
          require('copilot.suggestion').accept()
        else
          vim.api.nvim_feedkeys(vim.api.nvim_replace_termcodes('<Tab>', true, false, true), 'n', false)
        end
      end, { desc = 'Super Tab', silent = true })
    end,
  },

[micahkepe]

+1 on this issue

[Sirikakire]

+1 also experienced this

[GitMurf]

I am experiencing this as well and for what it is worth, this is the first time I have noticed it so it must be something more recent.

I am on Windows 11 and most recent neovim nightly.

[KorigamiK]

This is issue should be assigned on priority

[YiHui-Liu]

same issue after switching from copilot.vim to copilot.lua

[zbirenbaum]

I can't seem to reproduce this. I updated neovim to the most recent version, re-authenticated copilot, and pasted this config directly.

I noticed one comment reported using windows 11. Is everyone else having this issue on windows as well?

[micahkepe]

I'm on Mac

[karamanliev]

Nah, I'm on Linux.

[GitMurf]

I can't seem to reproduce this. I updated neovim to the most recent version, re-authenticated copilot, and pasted this config directly.

I noticed one comment reported using windows 11. Is everyone else having this issue on windows as well?

@zbirenbaum do you use Lazy for package manager and more importantly lazy load copilot so it does not load the plugin immediately at nvim startup?

I believe the issue is because I for example lazy load on 'InsertEnter' so if I open a buffer the first time in nvim session, press i to go into insert mode to start typing (that triggers copilot to load) and if I start immediately typing then it tries to send a request to copilot local server, but the server is not started up yet so it returns that error.

For others, can you confirm reproducing (especially if you use insert enter to lazy load) by opening a buffer and going to insert mode but do NOT start typing right way... wait a few seconds to start typing... then see if the error occurs as I get no error if I wait.

So @zbirenbaum the TLDR is that whatever recent change happened in the plugin and/or in Neovim core itself (or possible in copilot server itself), there should be some sort of check maybe to see if the copilot server is started up yet or not.

For me the immediate solution is to just lazy load on filetype enter so it loads as soon as I load a buffer instead of waiting for InsertEnter.

[karamanliev]

I believe that the example installation in the README is recommending lazy loading by InsertEnter as well, so he probably uses lazy nvim and lazy loads it.

For others, can you confirm reproducing (especially if you use insert enter to lazy load) by opening a buffer and going to insert mode but do NOT start typing right way... wait a few seconds to start typing... then see if the error occurs as I get no error if I wait.

I can confirm that.

[NeckBeardPrince]

Any updates to this?

[NeckBeardPrince]

Anybody know if a way to at least disable the error?

[NeckBeardPrince]

Wild

[karamanliev]

If you use noice.nvim you could silence it:

require('noice').setup({
...
        routes = {
          {
            filter = {
              event = 'msg_show',
              any = {
                { find = 'Agent service not initialized' },
              },
            },
            opts = { skip = true },
          },
        },
...
})

[xdannyrobertsx]

+1

[NeckBeardPrince]

Still getting this

[GitMurf]

Any update?

[GersiD]

On Arch Linux, Neovim version

NVIM v0.11.0-dev-1876+g86046c5a31
Build type: RelWithDebInfo
LuaJIT 2.1.1736781742

Lazy plugin manager, tried not lazy loading at all, still gives the same error message.

For repro, as soon as you get control of a buffer, press i to go into insert mode then press enter to start a newline. The speed with which you need to do this cannot be understated, the issue is non-existent without sufficient speed.

Likely best course of action is to ignore the notification with noice and go about my business.

[AntoineGS]

I someone wants to test out the PR I made for the fix you can temporarily change your config to pull from it like:

return {
  "AntoineGS/copilot.lua",
  branch = "fix_RPC",
  ...
}

[iFarmGolems]

Unfortunately I still experience this error...

2025-03-25 15:39:37.773 [4] [ERROR]: RPC[Error] code_name = ServerNotInitialized, message = "Agent service not initialized."

I use Neovim 0.10.4 on Arch system (with LazyVim)

My config

I use the master version of the plugin:

Also, there is this error in lsp.log:

[ERROR][2025-03-25 15:39:36] ...lsp/handlers.lua:623    "[default] Error sending telemetry FetchError: The operation was aborted\n    at fetch (/home/patrik/.local/share/nvim/lazy/copilot.lua/copilot/node_modules/@adobe/helix-fetch/src/fetch/index.js:99:11)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at runNextTicks (node:internal/process/task_queues:64:3)\n    at processTimers (node:internal/timers:516:9)\n    at cachingFetch (/home/patrik/.local/share/nvim/lazy/copilot.lua/copilot/node_modules/@adobe/helix-fetch/src/fetch/index.js:288:16)\n    at H2e.fetch (/home/patrik/.local/share/nvim/lazy/copilot.lua/copilot/lib/src/network/helix.ts:94:22) {\n  type: 'system',\n  _name: 'FetchError',\n  code: 'ABORT_ERR',\n  errno: undefined,\n  erroredSysCall: undefined\n}"

[AntoineGS]

A complete shot in the dark but could you try the beta branch? It needs more testing before I merge it into master but I would be curious to see if the change to the latest binary of Copilot makes a difference.

[iFarmGolems]

I've tried it and it still does not work. However, I found this which might be relevant since I've had some problems with certificates lately: https://github.com/orgs/community/discussions/121812

Your plugin works normally on a fresh install of Arch with the same package versions. This issue is on my side somewhere.

[AntoineGS]

Ah that sucks :( I hope you find a solution that does not require a fresh install! I will close the issue for now, though if anyone reports back that the issue still persists I will reopen.

[iFarmGolems]

Just so you know, it's also broken on the fresh distro Alpine WSL

What's funny is that it works some time after cleaning and reinstalling the plugin (for like 2 minutes) and then I get the error Agent service not initialized.

This is not an issue with your plugin but at least you can tell people that the problem is elsewhere.

I do believe that this would not appear on Ubuntu for example.

[julianpoy]

I'm getting this. Rolling back to 30b98a4c25d6152c14084020f703b6d56e1f1122 fixed it.

[apep-1998]

Hey, I changed my node version from 24.x.x to 22.21.0 and it worksss :D I use Arch btw :D