Is Context_custom setting used for autocomplete? How can it be harnessed?

[KingWebsites]

Hi, I'm trying to improve the autocomplete suggestions from a Qwen 2.5 Coder 7B (FIM) model running on my NVIDIA 4070 Super and I saw there was a "Context_custom" option in the plugin's settings.

Can somebody confirm that values in here would be used by autocomplete?

Would this be the best area to help improve FIM responses, or should a USER.md file be added to a project's folder?

My main work is with SCSS, JS and TWIG/PHP. Ideally when editing SCSS files I'd want to suggest contents of my _variables.scss and _mixins.scss files, and it would be good to include some very simple TWIG conditionals tailored to my WordPress/ACF setups. Could these be added to context?

Thank you in advance.

[shreyanshjain1]

I’m not 100% sure Context_custom is specifically wired into autocomplete/FIM the same way it might be used for broader chat/instruction context, so I’d be carefull about assuming it’s the best lever for completion quality unless someone from the project confirms that.

My guess would be:

• if Context_custom is used at autocomplete time, it’s probly better for general stylistic/project guidance
• but for the kind of examples you mentioned (_variables.scss, _mixins.scss, simple Twig/ACF patterns), the strongest signal is usually still the actual project files / nearby code context

So if the goal is better FIM suggestions, I’d personally prioritize:

1. keeping those SCSS/Twig helper files in the project so they’re part of normal repo context
2. making sure naming/patterns are consistent across the codebase
3. using Context_custom only for short high-level guidance, not as a big dump of code snippets

Something like this seems reasonable for Context_custom:

• preferred SCSS conventions
• naming rules
• common ACF/Twig patterns
• “prefer existing mixins/variables over inventing new ones”

But I probably wouldnt use it as a replacement for actual source files like _variables.scss or _mixins.scss.

So short version:

• I wouldnt assume Context_custom is the main autocomplete lever
• I’d treat it more like lightweight steering
• and I’d expect real project files / repo-local patterns to matter more for FIM quality

Would definitely be nice if someone from the project could confirm whether Context_custom is injected into autocomplete requests specifically, because that’s the key detail here.