omnirun

If somebody told me 2 years ago that I'd be building applications and websites, I would have laughed at them. I can't code. Still can't, really. But today I have a full desktop app built with Tauri, React, TypeScript, Zustand, SQLite, and Supabase. Every line was vibe coded. Not a single one written by hand.

The app is called omnirun. It started because I was frustrated with the tradeoffs in AI coding tools. Bolt.new is great for quick prototyping but you're trapped in a browser sandbox - no real files, no long-term maintenance, painful exports. Claude Code is powerful but it's terminal-only. I wanted something in between. A desktop app with a real UI where anyone can describe what they want and get it built, while owning the actual files on their machine.

What it does

You type or talk, and it builds websites, tools, automations, whatever you describe. It works with Claude, OpenAI, Gemini, Groq, DeepSeek, Ollama, and any OpenAI-compatible API. Bring your own keys, no markup.

Almost everything is stored locally in SQLite - project data, chat history, settings, memory, connections. Supabase only handles auth, billing, teams, and analytics. Your code never leaves your machine.

Features I'm most proud of

Auto model routing when using Claude - the app picks the right model per task automatically. Haiku for cheap stuff, Sonnet for building, Opus for hard problems. Cuts token costs 60-80% without the user doing anything.

Project memory - a context file that remembers your tech stack, decisions, and preferences across sessions. Close the app for months, come back, it picks up where you left off.

Time Machine - auto-snapshots before every file write. Unlimited version history with instant rollback. When you vibe code, you break things. This saves you.

Assistant section - completely separate from the builder. A personal AI agent connected to Gmail, Google Calendar, GitHub, Slack, Notion, Todoist. It reads your emails, drafts replies, and has watching agents that notify you when things happen.

What I learned vibe coding for 2 years

The hardest part isn't building. It's architecture decisions. AI can write code all day but it won't tell you "this decision will bite you in 6 months." I had to learn that the hard way multiple times.

The second hardest part is staying consistent. Two years is a long time to work on something with zero users and zero revenue. Some weeks I didn't touch it at all. Then I'd come back and the project memory I built would catch me up instantly — which is funny because I built that feature for future users, but I ended up being the first one who needed it.

Where I'm at now

Pre-launch. Getting close to a public beta. Currently building the waitlist and collecting early feedback.

https://omnirun.app

Happy to answer any questions about the build, the stack, or what it's like to vibe code something this complex as a non-dev.

Discord for early access and updates: https://discord.gg/3RCcuS9WWC