Patrick Lamar

Maybe there should be a default fallback fg color when hl group is not defined and can be configured in the config.

for others who met the same problem, you can just create a `TextInfo` and `TextMuted` highlight group as a workground. for example: ```lua vim.api.nvim_set_hl(0, "TextInfo", { fg = "#e0def4" })...

Yes, this can definitly work, but the only worring is whether it will work well with every colorscheme. Maybe providing a config like [this](https://github.com/akinsho/bufferline.nvim/blob/64e2c5def50dfd6b6f14d96a45fa3d815a4a1eef/doc/bufferline.txt#L806) in bufferline.nvim will be better?

> Quick question: does your colorscheme have the `Label` highlighting group? You can check it by using `:hi Label`. I think it could perfectly match as a `TextInfo` group replacement...

arch: ohhh, shit :)

It looks like that the request to plugin return 405 error. I use the self-hosted lobechat on vercel, it is the latest version

> > at the request to plugin return 405 error. > > Please check the error on vercel log, and show me > TypeError: Can't modify immutable headers. at (node_modules/@lobehub/chat-plugins-gateway/dist/cors.js:79:14)...

> 能方便看下安装的 `@lobehub/chat-plugins-gateway` 这个版本么？ not familiar with vercel, can you help to tell me where can i get the installed version of this package

> > not familiar with vercel, can you help to tell me where can i get the installed version of this package > > which package manager do you use?...

> I use LM Studio to start a local server with success, you can try to use http://localhost:11434 in the externsion options API URL. Only fill the api field with...