I ranked every vibe coding app

Vibe coding tools are multiplying fast—but the real differentiator isn’t raw coding power. It’s how well each tool lets non-experts “drive” toward an outcome without getting bogged down in terminals, code navigation, or developer-only workflows. In a tier-list-style ranking, Theo - t3․gg places tools on a “vibe” scale based on how much they hide implementation details, how much steering they require, and whether the experience feels designed for people who want results rather than mastery.

At the top of the practical “vibe” tier sits Cursor, largely because it behaves like an assistant you can actively steer—when you’re in the right mode. Cursor is described as the IDE of choice for Theo - t3․gg, with a key limitation: it’s strong when “driving” the agent, but weaker at autonomous steering. The interface also shows code prominently, which the ranking treats as a negative for vibe coders who prefer not to look at code at all. That same logic pushes several mainstream developer tools down: VS Code with Copilot lands in F tier because it’s fundamentally for coders, not vibe coders.

Windsurf lands in B tier. It started as a plugin-focused alternative and pivoted into a full IDE, but its defining feature is agent mode that can run its own commands—install packages, set up scripts—without the user micromanaging keystrokes. Theo - t3․gg also frames Windsurf as better suited for less competent developers, even noting that many users appear not to be engineers. Kira lands between Cursor and Windsurf: it’s built around spec-driven development, generating massive, hundreds-of-lines markdown plans before writing any code. That structure feels “corporate” and assumes a large existing codebase, making it less ideal for starting from scratch—yet it still matches the vibe of planning-heavy automation.

Trey is initially placed in B tier, then bumped to A tier after a demo that produces “illegible text” and “stunning images” in solo mode—an experience Theo - t3․gg describes as screaming vibe coding. The ranking is sensitive to friction: Trey’s solo mode requires upgrading to Pro and even a waitlist, which holds it back despite strong output.

Cloud Code, Open Code, and Codex illustrate the ranking’s tension between autonomy and vibe. Cloud Code is treated as an early “vibe coding for devs” tool because it hides code and pushes work into background execution, but it still forces users to watch the terminal. Open Code is instantly F tier because it refused investment—an explicit personal bias that becomes part of the meme. Codex is high-ish thanks to GPT5-powered coding success, but it drops because the project moved from TypeScript to Rust, which Theo - t3․gg calls the wrong “vibes” for vibe coders.

The ranking then tests “no-code” style apps: V0ero (now positioned as “no coding needed”), Bolt, Replet, and Lovable. V0ero performs well because it supports a prompt-first workflow and avoids terminal steps, earning A tier. Bolt and Lovable land in B tier due to UI clutter, integration friction, and errors that would be easier for developers to fix. Replet is also B tier, largely because it’s slow and doesn’t deliver the expected smoothness.

Finally, the list widens to other tools and even a “vibe coding demo” built on Convex (Chef). Chef can run full-stack with integrations, but it’s judged too developer-oriented, landing low. The overall takeaway is blunt: the “best” vibe coding tool is the one that minimizes steering, hides code, and gets to a usable outcome with the least cognitive overhead—while tools that demand developer knowledge, terminal fluency, or deep configuration tend to fall.