The Editor

Point at any screen, describe the change in plain language, and Brimeo rewrites the interface live. The request is checked against your declared Manifest, executed inside an isolated QuickJS-WASM sandbox, then committed as a structured overlay — your source code is never exposed to the user, and nothing runs that wasn't already declared.

vendor-app components LoginButton.tsx
1import { useState } from "react";
2
3export function LoginButton() {
4 // agent-editable region
5}
📁checkout-flow
Ask anything, @ to mention, / for actions

The Control Room

Every request runs inside a regulated environment: scoped permissions, a hash-chained audit trail, and an approval gate in front of high-impact actions — recorded pending before it reaches your backend, so an unlogged mutation can never start.

Everything that comes with it

Two of these you'll use every day. The rest are what make it safe to leave running unattended.

Live preview

See the reshaped interface exactly as it will look before anything ships to real users, or gets committed as an overlay.

Full audit trail

Every change is attributed, timestamped, and reversible — recorded in a hash-chained log before it ever reaches your backend.

Scoped permissions

Every edit is bounded to the surfaces a role is allowed to touch.

One-click rollback

Undo any agent change instantly, no engineering ticket required.

Structured, not text diffs

Overlays are name-keyed against the Manifest, so they reconcile through a three-way merge instead of a positional patch.

Agent-ready by default

Every declared Action is exposed as an MCP tool, and external MCP servers can be pulled in the same way.

Generated UI, isolated

GenUI output renders in an iframe with a strict CSP and zero network egress — never eval'd inline.

Durable, not one-shot

Standing workflows defined in natural language run through the same sandbox and governance path as any manual edit.