Vibe edit · evolutionary backbone
Point at it.
Describe the change.Ship it.
Edit your live sites in the browser like you would in a sketchbook. Underneath, the platform watches where the agent struggles and grows new skills exactly there — so the easy stuff stays easy while the hard stuff stops being hard.
How it works
Three motions, no ceremony.
- 01Step
Point
Open any deployed site. Click the inspector. Pick the element you want to change.
- 02Step
Describe
Type the change in plain language. Drop in screenshots, brand assets, voice notes.
- 03Step
Ship
Agent edits, opens a preview deploy, you approve, it merges. No build server to babysit.
The differentiator
The platform grows under you,
not next to you.
Most coding tools peak at the demo. They feel magical for a week, then you hit the same friction over and over and quietly accept it. We log that friction as pressure, and when a phase crosses the threshold the substrate writes a draft skill against it.
You read the skill. You install it. The next attempt is a single shot. Multiply by months and the agent is no longer a generic tool — it's a practitioner of your work.
- 01
Pressure
Every retry, repair, permission block, context overflow, and operator override is logged with weights.
- 02
Detection
Phases above the threshold surface as candidates. The system isn't guessing — there's a ledger.
- 03
Skill emergence
A draft skill is written for the recurring pressure. You review it; once installed, the agent reuses it without thinking.
- 04
Compound
Skills layer. Generation N+1 carries the kit Generation N earned. The platform does not plateau.
What you get on day one
A working substrate, not a shell.
Vibe edit any live site
Inspect, intent, ship. Same surface for landing pages, commerce, dashboards. The agent edits in a sandboxed branch and opens a preview deploy you can share before it merges.
Skills auto-emerge
When the same kind of edit takes 5 attempts twice in a row, the platform drafts a skill. You read it, install it, and the next attempt is one shot.
Publish what you ship
Generation builds, skill bundles, full project kits. Browse, fork, evolve from someone else's substrate instead of starting cold.
Bring your own keys
Anthropic, OpenAI, OpenRouter, gateway. Your spend, your usage caps, your audit trail. We don't middleman inference.
Same backend, local or cloud
The desktop app and the browser surface call the same agent endpoint. Edit local code with full filesystem access, or edit deployed sites in a tab.
Every edit leaves a trail
Each session writes a phase, a task, and an attribution stamp. The audit log is the planning system — not a separate compliance ritual.
Marketplace
Don't start cold.
Browse generation builds, skill bundles, and full project kits. Fork any entry and evolve from there. Ship yours back to the registry the same day.
Pricing
Open platform. BYOK. No per-seat fees.
Run the whole thing on your own keys. We make money when you publish to the marketplace and when teams want managed hosting — not by gating the editor or upcharging inference.
One edit away
Open the editor.
Make a change.
Vibe edit a live site or browse what others have shipped. Either way, the substrate is already keeping a ledger.