Missing chat language server URL

[DajmondFM]

After opening chat app its show this error message. Autocompletion works normaly.

{
  "url": "http://127.0.0.1:59791/?api_key=MY API KEY",
  "connection": {
    "status": "CONNECTING",
    "error": {
      "name": "Error",
      "message": "Missing chat language server URL. Please ensure that you are signed in to the Codeium plugin and close / reopen the chat window. If the problem persists, please restart the IDE."
    }
  },
  "isChatEnabled": false,
  "handshake": {},
  "params": {
    "ideTelemetryEnabled": false,
    "ready": true,
    "apiKey": "15be80b2-8251-4c9c-8056-16ea4abf4f81",
    "hasDevExtension": false,
    "hasEnterpriseExtension": false,
    "diffViewEnabled": false,
    "openFilePointerEnabled": false,
    "insertAtCursorEnabled": false
  },
  "data": {
    "numMessages": 0
  },
  "bridge": {
    "bridgeType": "null"
  },
  "health": {
    "checkStatus": null,
    "error": {
      "name": "TypeError",
      "message": "Failed to fetch"
    }
  }
}

[aliaksandr-trush]

"isChatEnabled": false,

Did you enable chat in config?

[DajmondFM]

Yes i have enabled chat in config.

return {
  "Exafunction/codeium.nvim",
  dependencies = {
    "nvim-lua/plenary.nvim",
    "hrsh7th/nvim-cmp",
  },
  config = function()
    require("codeium").setup({
      enable_chat = true,
    })
  end
}

Thats how my config looks

[vendion]

I get a sightly different error, even with the chat server installed.

   3 Error executing vim.schedule lua callback: ...ackages/start/vimplugin-codeium.nvim/lua/codeium/api.lua:426: attempt to concatenate field 'chatWebServerPort' (a nil value)¬
   2 stack traceback:¬
   1 >···...ackages/start/vimplugin-codeium.nvim/lua/codeium/api.lua:426: in function ''¬
 69  >···vim/_editor.lua: in function <vim/_editor.lua:0>¬

[gmdevz]

I have the same issue, does anyone here know how to fix this? will be using codeium.vim for now its working okay in on that extension atm

I hope this will be fix / have any solution for this

[pqn]

@fortenforge this seems similar to something you fixed recently in some extension I feel?