Co-Founder & CTO @HenosiaHQ • Creator of GraphQL plugin for WebStorm/IntelliJ

Where Design meets Code
Joined October 2007
Your favorite stack has a new visual editor. Your code. Edited at 60FPS. With @HenosiaHQ. @shadcn​/ui @radix_ui @tailwindcss @nextjs
8
16
5
161
37,231
Makes me think we need LLM benchmarks where the models don't get to pick their best next token. Think LLMs that are virtually tired, unconcentrated, drunk even. Can they still complete the task reliably 😁
There is still such a weird uncanny valley with even the best coding models. Gpt-5-codex rips through changes all day for five hours. Great. Then... Instead of updating the various task docs with progress (like it did fine all day) it decides it needs to delete the doc and recreate it with updates (losing 90% of the doc.) No human would ever make this mistake. I had to restore it from git and tell it to edit the damn doc properly.
1
288
Small but mighty update: Henosia AI now has tools to read the browser and server logs for the preview. This helps it debug and fix issues even faster 🚀
3
2
1
4
780
People are vibe coding websites and apps like crazy here in '25, empowered by AI. Vite has taken most of the uptake compared to Next.js, likely due to being less resource intensive to host for the vibe coding platforms. For now we're sticking with Next.js as our default. We've got the infrastructure to run it, and most pro teams prefer it over Vite. It's much easier to translate between prototype and production within the same web framework. Next.js also allows our AI to quickly make back-end edits, whereas Vite projects typically involve managing Supabase edge functions remotely, outside the regular git versioning flow.
I did a survey on the most popular AI app builders, asking each to "build a simple app with their default stack". Here's what I found what they default to: Bolt -> Vite Replit -> Vite Lovable -> Vite Convex Chef -> Vite Windsurf -> Vite Tempo Labs -> UI requires explicit selection but defaults to Vite v0 -> defaults to Next and supports Next only Firebase Studio -> defaults to Next even when the prompt contains "use Vite", but can use Vite if forced to. Buggy though.
3
250
Seriously impressed with the @elevenlabs text to voice v3 model. It's incredible for voice over in marketing videos. Also tried their music app. It made a hilarious 80s aerobics track. Still struggling with steering the music outputs. Really needs UI to edit instruments etc.
1
1
160
My main problem is knowing what instruments are called, sub genres to steer towards. Huge opportunity to make the output space explorative through UI and visualizations.
101
Introducing v2 of Henosia's Supabase integration: We show the UI to connect Supabase in the chat, plus you can pick which Supabase component blocks you need for your project. Under the hood we've also made improvements to how our agent manages the Supabase database for you.
1
3
264
What's the story on prompt caching for gpt-oss? Not seeing any mention of it by the providers. @GroqInc @cerebras
105
Cooking up something fun for Henosia in the coming weeks.
1
98
What's your favorite prompts to test in vibe coding tools? I'm currently obsessed with "SoMe for [animal]". Claude is comedy gold in that genre 😂
1
5
390
Getting such good vibes from Claude in @HenosiaHQ. It absolutely nails the color palette for "SoMe for squirrels": "Let me start by updating the theme to have a squirrel-friendly color palette. I'll use warm browns, oranges, and forest greens to create a nature-inspired theme that would appeal to squirrels.‍‌​" 😂
1
2
256
Me: Let's use JSON for chat history. It's industry standard. User: Proceeds to generate 232MB JSON for a single chat thread by pasting specs, logs, and images. Our WebSocket server: Nope, not sending that. The joys of production 😂
2
96
A sneaky Chrome devtools footgun: If you use "emulate a focused page", the Document.hidden and Document.visibilityState properties never indicate that a tab is hidden. Found this while ensuring we only play notification sounds for background tabs 😅
2
145
Claude's penchant for `npm run dev` is at Golden Gate Claude levels. @AnthropicAI check your weights 🤣 Yes, I've asked it not to in a 1000 different ways. Still sneaks 'em in.
2
157
Cursor famously forked VS Code. We put VS Code into your browser, so vibe coding is only a browser tab away. Because at its core, vibe coding is about access and excitement. Going from idea to reality, fast, in ways that were impossible only a few years ago. For the majority of people, their browser is the perfect way to get into vibe coding, so that’s where you’ll find Henosia. Ok, so vibe coding in the browser. Easy, right? Not quite. Let's dive into three challenges we faced: 🟣 Infrastructure Imagine you’ve got 2 seconds to create a working development environment for a new hire, and that environment needs to be fast, complete (a real Linux OS, with disk storage), and fully isolated from other environments since you’re sharing the server with other companies. We had to dig deep for this one, but I’m happy to report that we’re now at 1.8 second startup times thanks to techniques like memory snapshots for our Micro VMs. 🟣 AI Agent tooling Now, you’ll be chatting with our AI coding agent to make your ideas become reality. Agents are useful because of three things: The context you give them, the tools they have access to, and their own raw intelligence. The tooling side is specifically why we chose to embed VS Code in the browser for you. That way, our agent has a real IDE to do its things, and if you want you can also benefit from the best-in-class code editor that VS Code provides. For example, as our agent writes code in a file, the VS Code editor runs error checking and instantly feeds that information to the agent, which can then fix the any problems before moving on. We’ve found that this greatly improves the success rate as codebases grow. The coding agent is great for many things, especially heavy lifting in the codebase, but we’ve kept the best parts of Henosia's design tool heritage: 🟣 Visual editing and AI accuracy Visual edits are for what we call last mile design. Those last 20% where you want to precisely control the pixels. You’ll build faster and use fewer AI messages in the process. Win-win. We’re excited to see what you’ll build with Henosia. Already, we’re seeing people get into flow state, with around 4 hours of continuous vibing! Start building now for free at henosia dot com.
2
3
259
It evolved from a visual code editor and feels like it’s Lovable mixed with Cursor and Figma. You’re coding, then suddenly clicking on things to jump to the relevant code. Then, casually, tweaking padding in the inspector or shuffling components around right in the view. Still rough, missing my 196 VSCode extensions, but this feels like the future.
Replying to @HenosiaHQ
@HenosiaHQ is live with enhanced vibe-coding – where AI builds, but you perfect: - AI handles the heavy lifting - You fine-tune with visual edits (no code rewrites needed) The result? You build faster, cheaper, more accurately, and with fewer errors. #vibecoding
3
3
301
Replying to @HenosiaHQ
@HenosiaHQ is live with enhanced vibe-coding – where AI builds, but you perfect: - AI handles the heavy lifting - You fine-tune with visual edits (no code rewrites needed) The result? You build faster, cheaper, more accurately, and with fewer errors. #vibecoding
1
5
2
9
983
I intentionally asked @HenosiaHQ to use a Lucide `Sneakers` icon that doesn't exist, and it came up with a creative solution: Write and run a node script that extracts the available icon names in my installed Lucide icons package 😁
1
1
207
Build errors kill the good vibes. Hensosia automatically checks for build errors when it's coding, and fixes them right away. It's faster vibe coding without those pesky "Fix the build error you just made" clicks and interruptions. Details in 🧵
1
2
1
122
Henosia runs in your browser, but we've packed the full power of VS Code into Henosia. The means we're able to detect code errors with the same level of detail as Cursor or Windsurf. In this example we're relying on the TypeScript errors in the editor after Henosia wrote code.
1
1
49
As an added bonus, you have a fully working VS Code editor at your fingertips in case you want to take the wheel. No need to Git push/pull to quickly edit the code.
55