Option to disable the plugin for a list of specific models

[kevincojean]

Hello again,

Given using DCP's cache pruning has a small chance to confuse an LLM in certain scenarios, and given there are free models available with opencode like big-pickle and grok-code, I think it may be of use to allow users to specify a list of models for which the DCP plugin does nothing.

What do you think?

Cheers,

[Tarquinen]

I'll think about it, ideally I want to get DCP to a state where it works well with any reasonably recent model (which big-pickle and grok-code definitely are) so this isn't an issue. Trying to also not have too much config bloat, think the config is already a bit of a mess.

[cau1k]

I think it makes sense to offer model or provider specific settings. It works fantastic with Copilot models but I prefer to rely on prompt caching for providers that offer full context. Happy to look into this if it's on the roadmap.

[Tarquinen]

Yea thats a strong argument, feel free to help out with a PR if you're interested, use the dev branch.

[Tarquinen]

I did some research into this, currently opencode tools are loaded on initialization, and there isn't a clean way to enable or disable them based on the model picked after initialization. DCP uses a number of strategies, and everything other than custom tools (I think) can be disabled based on chat parameters such as provider/model being used, but I don't really like a solution where some parts of DCP are disabled but others persist.

Let me know what you think, especially if you have any ideas on how we can get around this.