I've been using GitHub Copilot and Codeium together for the past few months, and honestly they're getting in each other's way. Every time I start typing, both extensions trigger suggestions and it's slowing me down more than helping. Should I just pick one, or is there a way to configure them so they don't conflict?
The folks above are right that running both is noisy, but before you kill one entirely, try disabling just the popup UI on whichever you use less - most completion extensions let you turn off suggestions while keeping manual triggering (Ctrl+Space) available. That way you get the best of each tool when you actually want it, without the constant chatter.
What's your actual workflow - are you finding the suggestions genuinely useful, or are they just creating visual noise? If it's the latter, honestly the simplest fix is to disable one of them. Running both simultaneously is almost always overkill and will tank your editor's responsiveness. Most people find that picking the one whose suggestion style matches how they code works way better than trying to manage two at once.
If you do want to keep both (maybe you like different features from each), you can configure them to take turns. In VS Code settings, you can disable autocompletion for one extension and trigger it manually via keybind when you actually want it. For example, keep Copilot on autocompletion but set Codeium to only show suggestions when you hit Ctrl+Shift+A or whatever hotkey you prefer. You'd also want to disable inline suggestions for whichever one you're using less frequently - that's usually where the conflicts and slowdown happen.
The real move though is just picking one that feels right and uninstalling the other. Test them separately for a week each if you haven't already. Copilot tends to be more opinionated about code style, while Codeium can feel a bit more flexible, but that varies by language and project. Your editor will run noticeably smoother with just one AI assistant, and you'll actually be able to focus on coding instead of dismissing popups.
Picking one is genuinely the way to go here. Running both simultaneously creates exactly the problem you're describing - competing suggestion popups, latency issues, and mental overhead deciding which one to dismiss. If you want to test-drive the other one later, just disable it in VS Code's extension menu rather than uninstalling, so you can flip back without reinstalling. Most people find they get faster and more focused once they settle on whichever one feels more natural for their coding style.
have you actually timed how long you spend dismissing popups vs typing code? because that's the real measure here 🎯
running two completion engines at once is basically having two people shouting suggestions while you're trying to think. the latency stacks up, your brain gets context-switched between competing UIs, and you end up spending mental energy just picking which one to ignore. most folks find one solid tool ends up way faster than two mediocre ones fighting for attention.
my take: disable one entirely and actually give the other a full week of use before deciding it's the right fit. if you go this route, you can tweak the keybinds so completions don't auto-trigger - set it to only show on explicit command (like ctrl+space or cmd+space). that way *you* decide when suggestions appear instead of getting bombarded constantly. some people also turn off the inline preview and only accept completions when they explicitly tab into them, which cuts down noise significantly. you might find that when suggestions aren't always screaming for attention, you're actually way more productive 💡
Log into answer.
