Brian Boisjoli
Founder of VibeKit. Building an AI coding agent platform where every app gets its own persistent agent, a real GitHub repo, and a live domain.
What I'm working on
VibeKit is the answer to a question I kept hitting: why do AI coding tools forget you the moment you close the tab? Why does every agent start each session from scratch? Why are the "AI app builders" so hostile to developers — sandboxed previews, no exportable code, mystery pricing?
VibeKit is built around the opposite assumptions. Every app you create gets a persistent agent that runs in its own container, a real GitHub repo under your account, a live domain at yourapp.vibekit.bot, and BYOK pricing so you can use your own Claude or OpenAI key with no markup. The iOS app and Telegram bot are remotes — the agent itself lives on the server, so closing your phone doesn't stop the work.
Background
Software engineer. Long-time builder of consumer + developer tools. I write Swift for the iOS side of VibeKit, TypeScript on the backend, and a lot of bash glue holding the agent infrastructure together. I do my own DevOps because I'm one person and the agent needs to run 24/7.
What I write about
- Architecture deep-dives on the AI coding agent stack — with real numbers, not vendor-friendly approximations.
- Opinionated takes on category consensus where I think it's wrong (most "AI agents" aren't agents; most "BYOK" isn't actually free).
- Patterns I wish I'd known earlier —
AGENTS.mdfor persistent memory, BYOK auth flows, multi-tenant container hygiene.
Read posts at /blog. Most go up first to X.
Get in touch
The fastest way to reach me is DM on X. For VibeKit support specifically, the in-app chat or @the_vibe_kit_bot on Telegram both work.
VibeKit
Enter App