Solo founder building *Vibe* — 3-tier AI copilot system:
1. *Chrome extension* (current MVP — API key, page commands)
2. *Chromium fork* (full browser with native AI copilot)
3. *Playwright agent* (headless, full DOM + accessibility tree access)
*Key insight:*
– Extension = limited (no accessibility tree, weaker context)
– Browser + Playwright = full power (HTML tree, real-time DOM, automation)
I was going to open-source the extension (MIT) to get traction/contributors.
But now: *90% of future value is in the browser + agent*, not the extension.
*Dilemma:*
– OSS extension → community grows shell, but I lose control of the real product
– Keep all closed → slower feedback, harder to validate
*Options:*
1. *Source-available extension* (public code, no forks/commercial use)
2. *OSS only the extension SDK* (API to plug into Vibe Browser)
3. *Stay fully closed*, launch browser beta first
LangFuse: MIT core + paid EE
Raycast: closed core, open extensions
*HN:*
– Should I OSS the weak part (extension) to build mindshare?
– Or keep everything closed until browser MVP ships?
– How to get early users without giving away the moat?
SF, 2 months runway.
Repo (coming): https://github.com/VibeTechnologies/VibeWebAgent
Pitch: pitch.vibebrowser.app
What would you do?
Comments URL: https://news.ycombinator.com/item?id=45936577
Points: 1
# Comments: 0
Source: news.ycombinator.com
