How can I control the context?

[einarpersson]

Hi!

I suppose the title says it all.

I use many ai-tools, for example aider, aichat and CodeCompanion. Setting the appropiate context is crucial for good output. However, I have yet to understand how / if it is possible to provide a certain context reliably to Copilot Inline Suggestions. If not, is there any other (perhaps indirect) way to do it that actually works somewhat reliably?

I have searched for answers on the web but most often find results that seems more relevant to Copilot Chat which is not what I am after.

This feels sooo central to getting better inline completions. Grateful for any comment.

(Typical example: I want to get better hints for Svelte 5. Currently the suggestions are typically Svelte 4 as the training data is limited. I want to insert a condensed cheatsheet)

Note: If the answer is NO, then please let me know and I can stop looking.

[einarpersson]

I found this in :h copilot

                                                *g:copilot_workspace_folders*
g:copilot_workspace_folders
                        A list of "workspace folders" or project roots that
                        Copilot may use to improve to improve the quality of
                        suggestions.
>
                        let g:copilot_workspace_folders =
                               \ ["~/Projects/myproject"]
<
                        You can also set b:workspace_folder for an individual
                        buffer and newly seen values will be added
                        automatically.

1. What does Copilot do if this value isn't set? I mean, if I am to set a value I'd like to know what I override. Does copilot try to "guess" a project root or does it simply have a narrower focus when the setting is not set?
2. How do you @tpope use this, or recommend to use it? One way is to just always set it to the project root, but if you have a big project it could perhaps lead to a big number of irrelevant files confusing the model? Would be super to just get a short hint on how to "maximize" the impact of this setting.

[Sakshivirang3826]

Yes

…

On Fri, 23 May 2025, 7:43 pm Einar Persson, ***@***.***> wrote: *einarpersson* left a comment (github/copilot.vim#115) <#115 (comment)> I found this in :h copilot *g:copilot_workspace_folders* g:copilot_workspace_folders A list of "workspace folders" or project roots that Copilot may use to improve to improve the quality of suggestions. > let g:copilot_workspace_folders = \ ["~/Projects/myproject"] < You can also set b:workspace_folder for an individual buffer and newly seen values will be added automatically. 1. What does Copilot do if this value isn't set? I mean, if I am to set a value I'd like to know what I override 2. How do you @tpope <https://github.com/tpope> use this, or recommend to use it? One way is to just always set it to the project root, but if you have a big project it could perhaps lead to a big number of irrelevant files confusing the model? Would be super to just get a short hint on how to "maximize" the impact of this setting. — Reply to this email directly, view it on GitHub <#115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BRJRIRP3VB7XC3CCEKVWVBL274UJ7AVCNFSM6AAAAAB5WO73VWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBUGU3DMNJTG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>