How did you feel using Qoder? Let’s hear it!
1 Like
So far so good, if you keep your pricing below the other overinflated BS AI IDEs like Cursor and Claude, and actually back it up with a robust model + fair usage billing, you’ll wipe the floor with the competition. Just advertise the real coder pain points and show how your platform solves them, nothing kills hype faster than exposing bloatware pricing.
1 Like
Here are my first impressions.
Importing is very simple, this will make onboarding people more likely onto Qoder.
The UI replicates what users in the niche are used to and have used for over the last year.
The model while its solely one, which is internal, seems to run smoothly, but could do with more tokens/second in response. Which we will see in the future without a doubt.
Looking forward to Qoder, taking the market from both Trae & Cursor.
The usage limit finished pretty fast and I’m changed to basic model, I don’t really know what that means.
这个积分的使用还是蛮快的，特别是现在会读取比较多的上下文的情况下，而且如果能开发插件适配命令行工具会是用户增长点的一个大部分，最好是主流的claude code和gemini CLI（QWEN Code）都支持可视化修改，可能会为IDE争取来使用命令行工具的用户，保证IDE用户保有量，而且IDE和命令行是相辅相成的，命令行适合修改代码，IDE则更适合了解和问答，了解和问答消耗的积分有限，反而会缓解积分消耗快还效果不如CLI工具的现状
Credits drain too fast - we need more credits and more usage details
I used up all 2000 credits in a single day. At first glance, Qoder seems very good and promising, similar to how Cursor felt some time ago. The issue is that the credits don’t appear to be tied directly to prompts—the way they’re consumed is a bit more complex. At least during this early stage, I believe accounts should have at least 10,000 credits in order to properly test the application.
The usage page only shows how many credits I’ve spent, without any detailed breakdown. We don’t fully understand how credits are consumed, which makes it impossible to optimize our processes, and this lack of transparency provides no predictability.
In our projects, we need to know what budgets to allocate, how much we’re consuming, and how we can optimize these costs. I really like your model—it clearly has potential, and I’ve seen that in some of the features already implemented. But in order for me to actually use it, I need predictability.
1 Like
Плохое впечатление, после авторизаци в https://qoder.com чат IDE все равно остается недоступным, с сообщением что как будто я из него вышел, возращаюсь обратно в CURSOR, сплошные баги.
不好用,wiki生成很慢，反而是Quest模式做的很有特色，个人认为可以扩展作为一个教学功能
It’s been absolutely fantastic for me, the best I’ve experienced, and I’ve used almost all of the other AI tools available. I’m not a vibe-coder, I’m a full-stack dev who uses Qoder for some of the more difficult tasks, and it’s been a real big help. I love the Repo Wiki functionality it has, which gives it a real understanding of a project. I just wish credits weren’t based on a time period, and when they ran out you could just buy more.