VibeKit
Enter App
Blog
Long-form writing on AI coding agents, persistent memory, BYOK economics, and what we're learning building VibeKit.
-
Why we picked AWS Fargate over WebContainers for an AI coding platform
WebContainers — the StackBlitz tech behind Bolt — boot in 2 seconds and feel magic. We picked the slower, heavier option (real Fargate containers) anyway. Here's why, and what it means for the kind of apps you can actually ship on the platform.
-
What persistent agents actually remember — and what they shouldn't
Every AI coding tool now claims 'persistent memory.' Most of them just have a longer chat window. Real agent persistence is a layered system: durable files, an indexed workspace, agent-side notes, and the AI provider's own context. Here's what we put where, and the few things we deliberately let the agent forget.
-
How AGENTS.md works (and why most AI coding agents need one)
AGENTS.md is the file every agent in VibeKit reads on every turn. It's not a system prompt — it's a per-app contract that scopes the agent's behavior, encodes architectural decisions, and survives context resets. Here's why it matters and how it's built.
-
BYOK vs platform-paid AI: the real cost of 1,000 features
Most 'all-in-one' AI coding platforms charge $20-40/mo and bake the AI cost into the subscription. Bring-your-own-key sounds nicer in theory. Here's the actual math on which model wins for which kind of user — with real per-task token measurements, not vendor-friendly approximations.
-
Why I'm starting this blog
Quick intro to what I'll write about: AI coding agents, persistent memory, BYOK economics, and the architecture decisions behind VibeKit. No 'top 10 tips' content.
-
Most 'AI agents' aren't agents — a definition that actually means something
The word 'agent' has been slapped on every LLM product launched in the past 18 months. Most of them aren't agents under any honest definition. Here's a tight three-property test, and how popular tools score against it — including VibeKit.