I think codecompanion.nvim should follow this [guide](https://github.com/neovim/neovim/pull/29073)

[brianhuster]

Currently, codecompanion.nvim put all initializing code in setup() function, which I think isn't nice as it forces users to call setup() function just to use the default config. That is not nice for people who don't use a package manager but just want to use built-in :h package feature with git submodule.

Neovim has built-in global-plugin that I think shoud be used for initialization instead of setup() function

I have sent a PR for it #750

[olimorris]

How does this affect those who do use a plugin manager? Of which I suspect is 95% of the user base?

[olimorris]

How are you setting up the plugin currently?

[brianhuster]

I would say there is no effect. The function `require'codecompanion'.setup()` still exists, anyone who already call it in their config would be just fine. For those who want to setup their config, they will still have to call `require'codecompanion'.setup()`. But at least those who are fine with default config (eg. me) don't need to do that, they can just drop the plugin to `packpath` and done. Vào 18:18 Th 3, 28 thg 1, 2025 Oli ***@***.***> đã viết:

…

How are you setting up the plugin currently? — Reply to this email directly, view it on GitHub <#751 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2VVX7N5OESD2SAYTSKIQ6L2M5RPLAVCNFSM6AAAAABWAF3AL6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJYGMYTGMQ> . You are receiving this because you authored the thread.Message ID: <olimorris/codecompanion.nvim/repo-discussions/751/comments/11983132@ github.com>