Copilot’s BYOK Blocking for Inline Completion Makes No Sense. [THE FIX]
GitHub Copilot allows Bring Your Own Key (BYOK) for its Chat window, but it explicitly blocks those exact same custom models from being used for inline code auto-completion.
The official justification from the VS Code team is a supposed "lack of capable FIM (Fill-in-the-Middle) models." However, this excuse doesn't hold water:
- It shifts blame incorrectly: If a user configures an incapable model for inline completion and it breaks, that is a user configuration error, not a flaw in VS Code.
- It ignores standard error handling: Why is the team over-policing the user's model choice? They could easily validate the model's response, throw a clear error if it fails to support FIM formatting, and offer a fallback option to the default Copilot model.
Instead of removing those few lines that blocks user defined models, the issue remains buried in the "forever-backlog" (see VS Code Issue #318545).
🔥 The Fix: A Community Solution That Actually Works: 🔥
Frustrated by this arbitrary limitation, I looked for alternatives and found a new extension that bridges the gap: GitHub Copilot LLM Gateway. (Thanks to the Andrew Butson and Contributors)
This extension enables true inline completion support for local and custom models. While it is still a work in progress and doesn't handle responses as flawlessly as the native Copilot integration just yet it proves that the functionality is entirely possible.
If you care about local LLM freedom and open-source control over your dev environment, consider checking out the repo and contributing to help perfect it!
The good news is that it's actually open source, so anyone can keep using it forever. Now let's just hope Microsoft doesn't "solve the problem" by removing it from the VS Code Marketplace. 😂