First off, I’m genuinely glad to be part of the Qoder community. I’m a pretty heavy vibe-coding user myself. I’ve tried and used Claude Code, Codex, iFlow, Trae, and Cursor. Right now my main tools are Claude Code, Codex, and, sadly, iFlow, which is apparently on its way out as of yesterday.
As a potential replacement for iFlow, Qoder still has some pretty obvious shortcomings. I get that your main focus right now is the IDE side of things — and honestly, it kind of feels like CLI users are being treated like an afterthought.
Qoder CLI’s MCP configuration is, bluntly speaking, the worst I’ve dealt with. Skills are whatever — at the end of the day, that’s just creating a folder. But MCP config? Even when I follow your own documentation step by step, I still can’t get it to work at all. Why is adding a global MCP configuration such a pain in the ass? I’ve run into the same issue on Linux Mint, Fedora, and Windows 11. I even fed the MCP install commands directly into Qoder CLI itself, and after it “installed” everything, it still couldn’t call it properly. To make things worse, the config files end up scattered all over the damn place. Claude Code and Codex definitely score points here.
Another issue: I have no problem with custom models on the IDE side being a paid feature — that’s clearly where your focus is. Fine. But not allowing custom models on the CLI side at all? That feels ridiculously out of touch with the competition. Codex, Claude Code, OpenCode, and iFlow all support adding custom models in the CLI. If you’re seriously still insisting that CLI custom models have to be paywalled too, then honestly, I’m speechless.
If you’re going to build both an IDE and a CLI, then your team needs to get on the same page and build both properly. Don’t half-ass one side while pouring everything into the other. Right now the imbalance is obvious, and if that keeps up, competitors in every segment are going to eat Qoder alive.