VibeKit
Enter App
Vibe Coding
Describing what you want to an AI agent and letting it ship the whole thing — framework, code, build, deploy, domain. You direct the vibes; the agent ships the bytes. Coined by Karpathy in February 2025. Now a workflow people actually ship production apps with.
Plain definition
Vibe coding is software development where the human's primary input is intent — described in natural language — and an AI agent does the implementation. The agent picks the framework, writes the code, runs the build, fixes its own errors, and ships the result. The human steers by reacting: "this should look different", "add login", "the table feels cramped", "deploy it".
"There's a new kind of coding I call 'vibe coding,' where you fully give in to the vibes, embrace exponentials, and forget that the code even exists." — Andrej Karpathy, Feb 2025
The shift from earlier AI coding (Copilot autocomplete, Cursor's edit mode) is that the agent owns the implementation loop. You're not editing what it suggests — you're reacting to what it shipped.
What it's good for
- Greenfield projects. A new app, a tool, a landing page, a Slack bot. No legacy constraints, no inherited weirdness. The agent picks reasonable defaults and ships.
- Prototyping ideas. Try ten product ideas in a week. Most won't work; one will. Vibe coding lowers the cost of "try it" to almost zero.
- Adding features to small codebases. The agent reads the whole repo, follows the existing patterns, ships consistent code.
- Coding when you're not at a desk. The phone, the couch, the bus. The agent doesn't care about your input device.
What it's bad for
- Hardening complex production systems. When a misread spec could cost a customer their data, the agent's confidence outruns its understanding.
- Performance / security work. Both require holding a lot of invariants in your head simultaneously. Agents are getting better here but aren't there yet.
- "I don't know what I want." Vibe coding rewards clarity of intent. If you can't describe it, the agent will ship something that doesn't fit.
The honest tool comparison
| Tool | Surface | Hosts the result? | Free tier? |
|---|---|---|---|
| Cursor | IDE (desktop) | No — you host | 14-day trial |
| Claude Code | CLI | No — you host | Pro subscription required |
| Lovable | Web UI | Yes (their infra) | Limited free credits |
| Bolt | Web UI (WebContainer) | Yes (their infra) | Limited free credits |
| Replit Agent | Web IDE | Yes (Replit infra) | Free with limits |
| VibeKit | iOS app + web dashboard | Yes (Fargate) | Genuinely free |
VibeKit's niche: vibe coding on the surfaces you already have open — your phone, your web browser — with the result hosted automatically and a genuinely free tier (not a trial). See vs Lovable, vs Bolt, vs Replit for specific comparisons.
How to actually start
- Pick a surface. Phone? Grab the iOS app. Desktop? Cursor or Claude Code.
- Pick a model. Cheap or free for prototyping (VibeKit's free tier = $0). Smart for hard problems (Claude Sonnet via BYOK on any platform).
- Describe what you want in one sentence. Not a spec — a vibe. "Web app that takes a youtube link and replies with a summary." "Next.js app for tracking books I want to read."
- React to what the agent ships. The conversation IS the spec.
Common pitfalls
- Over-describing the first prompt. Don't list 20 features. Ship the core, then iterate. The agent is faster than your spec doc.
- Letting tech debt pile up. Vibe coding ships fast; that's the gift and the trap. Periodically ask the agent to refactor what it's built so far before adding more.
- Vibe-coding sensitive code. Auth, payments, key handling — these reward reading the actual code. Vibe-code the scaffolding; review what touches money or secrets.
- Skipping git. Every vibe-coded app should have a real GitHub repo. VibeKit auto-creates one; other tools you have to wire up. Without git history, vibes don't replay.
FAQ
What is vibe coding?
Vibe coding is describing what you want to an AI agent in natural language and letting the agent handle the entire implementation — picking the framework, writing the code, running the build, fixing its own errors, deploying to a real URL. The human's job is product direction (what should this do? what's wrong with how it feels?), not syntax. The term was popularized by Andrej Karpathy in February 2025.
Is vibe coding real or just a meme?
Both. The term is half-meme — it captures a vibe, not a methodology — but the underlying workflow is real and shipping production software. Indie hackers build entire SaaS products this way; teams use vibe-coded prototypes to test ideas before committing engineering time. The honest framing: vibe coding works great for greenfield projects and small features, less well for hardening existing complex systems where the cost of a misread spec is high.
Who invented the term vibe coding?
Andrej Karpathy in a February 2025 tweet describing how he was building software by 'fully giving in to the vibes' — letting Cursor's agent mode handle implementation while he steered with natural language. The term resonated because it named something a lot of developers were already doing but didn't have a label for. Within months it became shorthand for the agent-first development workflow.
What are the best vibe coding tools?
Three categories. (1) IDE agents — Cursor, Windsurf, Claude Code. Best for developers who want vibe coding inside their existing editor. (2) Hosted vibe-coding platforms — Lovable, Bolt, Replit Agent, VibeKit. Best when you don't want an IDE; you want to describe an app and have it shipped to a URL. (3) Chat-driven agents — VibeKit's iOS app, ChatGPT with computer use. Best for non-IDE surfaces (phone, on the go). The right pick depends on whether you want to host the result yourself or have the tool host it for you.
Can I vibe code from my phone?
Yes — that's actually where the workflow shines because there's no IDE to compete with the agent. VibeKit ships a native iOS app and a web dashboard; both let you describe an app, watch the agent build and deploy it, then iterate by typing follow-up prompts. The 'vibes' part is the point: lying on a couch describing what you want is the actual interface.
How do I start vibe coding for free?
Sign up to VibeKit with Apple / Google, pick the free tier (free via OpenRouter's pool), describe your first app. The agent provisions a container, creates a GitHub repo, deploys to yourname.vibekit.bot, and waits for your next instruction. No credit card required. Switch to Claude / GPT-5 later if you hit the limits of free models.
What's the difference between vibe coding and no-code?
No-code platforms (Bubble, Webflow, Glide) give you a visual builder with predefined components — you arrange UI elements without writing code, but you're limited to what the platform exposes. Vibe coding generates real code that runs in a real container — same framework, same package manager, same Git history as a human would write. You can read it, edit it manually, or hand it to another developer. No-code locks you in; vibe coding gives you a real codebase from the start.