Codeium Problems & Issues
Real user-reported problems, complaints, and limitations for Codeium. Based on analysis of 12 signals.
Overall score: 60/100
Issues by Category
Modifications break existing code
When users ask Codeium to modify something or create a new feature, it reportedly 'starts to break things.' Code consistency across project files is lost. Users spend time fixing AI-introduced bugs rather than building features.
Concern over IDE extension deprecation
Users frustrated that Codeium appears to be pushing users toward proprietary Windsurf Editor, potentially abandoning VS Code and other IDE extensions. While extensions still work, they're in 'maintenance mode' with focus shifting to standalone editor.
Context understanding limitations
Reviews note context understanding issues - AI doesn't fully grasp project structure or coding patterns. Suggestions can be technically correct but contextually wrong for your codebase.
Missing features compared to competitors
G2 reviews cite missing features as a complaint. Lacks Composer-like multi-file editing that Cursor offers. Feature set trails premium competitors despite free pricing.
Documentation needs improvement
Documentation could use improvement according to user feedback. Setup guides and troubleshooting resources are incomplete. Users rely on community for help.
JetBrains plugin crashes constantly
The chat window of the JetBrains plugin crashes constantly with no support available, not even for paid subscribers. Users report having to restart IDE frequently. Plugin stability issues affect daily workflows.
Intermittent connectivity issues
Codeium sometimes struggles to connect to the IDE. Users report being unable to use it for days before it suddenly works again. No clear troubleshooting path. Random disconnections disrupt workflow.
VS Code extension requires frequent restarts
Some developers report occasional bugs in the VS Code extension that require IDE restart. While minor, frequent restarts interrupt development flow and add friction to the free experience.
Pro subscribers report terrible support
Paying Pro subscribers complain about poor quality, unusable code generation, constant resource issues, and completely unresponsive customer support. No option to report bugs on website or customer portal. Users describe experience as 'confusing and frustrating' given social media hype vs reality.
Unexpected billing charges reported
Some users report being unexpectedly charged for 70+ transactions in just a few days. Billing transparency issues and difficulty understanding charges. Combined with poor support response, creates distrust.
Slow performance and suggestions
G2 reviews cite slow performance as a common complaint. Suggestions can be delayed, affecting coding flow. Not as responsive as premium alternatives like Copilot or Cursor.
Rebrand confusion (Codeium vs Windsurf)
April 2025 rebrand from Codeium to Windsurf creates confusion. Users unsure if their extension is current or deprecated. Documentation references both names. Brand identity unclear during transition.
Regret Patterns
Common reasons users regret choosing Codeium.
Paid for Pro but support still nonexistent
Upgraded to Pro expecting better support for crashes and issues. Found that paid subscribers report same poor response - no option to report bugs, emails ignored. Paying doesn't improve the experience.
JetBrains plugin too unstable for work
Started using free tier for JetBrains IDE. Chat window crashes constantly, requiring frequent restarts. Eventually switched to Copilot despite cost because workflow disruptions were worse than payment.
Modifications broke existing code
Asked Codeium to add a feature to existing codebase. AI modifications broke existing functionality, requiring hours to fix. 'Free' ended up costing time. Learned to be extremely careful with AI suggestions.
Unexpected billing charges appeared
Signed up for Pro but saw 70+ unexpected transactions in days. Billing transparency poor. Support didn't respond. Had to dispute charges with bank. Trust completely broken.
Extension deprecated for Windsurf Editor
Invested time learning Codeium in VS Code. Realized extensions are now 'maintenance mode' with focus on standalone Windsurf Editor. Feeling pushed to switch IDEs to get best experience.
Company acquisition creates uncertainty
Became dependent on free Codeium tier. Cognition acquisition in July 2025 makes future uncertain. Worried free tier will be eliminated or degraded. Considering paid alternatives for stability.
When Codeium Breaks Down
Specific scenarios where Codeium fails or underperforms.
JetBrains plugin crashes repeatedly
Chat window crashes constantly with no support available. Development workflow disrupted. Must restart IDE frequently. No fix despite paying for Pro subscription.
Connectivity issues block work
Codeium randomly unable to connect for days at a time. No troubleshooting guidance. Developers left without AI assistance with no warning. Cloud dependency is single point of failure.
Support needed but unavailable
Issue arises requiring help. No bug reporting on website. Emails unanswered. Even Pro subscribers get no response. Must troubleshoot alone or switch tools.
Team scales beyond free tier limits
Started with free tier for team. Realize 25 prompt credits insufficient for real work. Pro at $15/user or Teams at $30/user adds up quickly. 'Free' was just a trial.
IDE extension deprecated for Windsurf Editor
Extensions in 'maintenance mode' while development focuses on standalone editor. Users of VS Code/JetBrains may face declining quality. Must decide whether to switch to Windsurf Editor.
Acquisition changes product direction
Cognition acquisition (July 2025) may change pricing, features, or free tier availability. Enterprise customers face uncertainty about long-term support and roadmap.