Change:
public async run(accessor: ServicesAccessor | undefined, editor: ICodeEditor): Promise<void> { const controller = InlineCompletionsController.get(editor); <del> controller?.model.get()?.trigger(undefined); </del> <ins> controller?.model.get()?.triggerExplicitly(); </ins> } }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --Version: 1.78.0-insider Commit: Date: 2023-04-21T05:39:53.263Z Electron: 22.4.7 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin arm64 22.4.0 Sandboxed: Yes the command the implementation method you have access to the which has a . The 2 possibilities here are and . The value here is always regardless of auto invoke or executing the command. This issue prevents the Copilot extension from distinguishing the triggers. Our users ask for a way to disable auto completions while still allowing manual triggers. It seems the is the correct way to determine this trigger but it doe snot work.
do you know if it is something that can be prioritised ? it is blocking one of our large customer
thanks for opening this issue. Can you share the user feedback? This feels like a UI interaction, and maybe we should have a setting on the VS Code side for this, and not on the Copilot side. Maybe once we finally tackle this interaction for your customers will also be improved. thanks for the ping, I can comment more once analysis this issue.
Sure, here are 2 examples: Having a VSCode solution sounds fine at first. Thinking about it I wonder how to name it. I mean, our customers do not know anything about an InlineCompletionProvider or so. They know Copilot, so they are looking for Copilot settings.

I think it would really help us if the existing API would just work. We also have a setting to completely disable inline completions already.
Thanks for sharing - this is great. feels unrelated to this, these folk have a problem of having multiple inline suggestion providers. Something we plan to tackle better on the VS Code side. sounds like a valid use case, and imho should be VS Code driven. Good point for having "Copilot" mentioned in the setting name for ease of finding. Can we first, better understand why users find Inline Suggestions annoying in this case. For example, is it because they are getting in the way of the Suggest Widget or it is completely unrelated. could you find this out? Let's see what thinks.
From what I gathered, it is not not entirely related to the suggest widget but also preferences of the team using it. In the case of our customer, they simply prefer to have control on when they get a suggestion. So this enhancement is just to provide a way to our user to have only manual suggestion if they wish to.
this is a regression. results in "Invoked" in 1.77.3, and "Automatic" in 1.78.0-insider ()
Thx for the fast fix! You guys rock
Thank you for the super fast turn around
can you please verify on your side if this indeed fixes the issue? This is included in the latest VS Code Insiders. Thanks!
I can confirm that the trigger does also have the value now. Unfortunately manually triggered completions are not showing up at all now . This still works in 1.77 but not in the latest insiders. I'm using:
thanks for letting us know. I can reproduce, and I opened a new issue