For engineers
You are the one being asked to allow this.
So here is the whole mechanism: what we read from your repository, where the code runs, what an editor can and cannot touch, and what happens to any credential you hand over.
Portability, honestly
Most tools ask you to describe your own environment. We just read the repo.
Revise reads lockfiles and manifests to suggest install commands, a preview server and supporting services. Laravel, Angular and other stacks each need different setup. A developer can review and correct the detected configuration before starting.
Detected Next.js 15 · pnpm · apps/web
install pnpm install --frozen-lockfile
dev pnpm run dev -- --hostname 0.0.0.0
port 3000
services postgres ← detected database dependency
secrets DATABASE_URL ← supplied by that container
AUTH_SECRET ← generated, 32 random bytes
STRIPE_SECRET_KEY ← stubbed; billing won't respond
NEXT_PUBLIC_URL ← the repo shipped a working default
Ready. Nothing needed from you.Recognizes common stacks
Signature matching identifies these frameworks. Detection is a starting point; custom infrastructure and private dependencies may still need your developer.
And when we can't
An unusual repo says so instead of inventing a command that fails three minutes into a build. A developer corrects it once, in a panel marked for developers, and nobody is asked again.
Build once, resume while available
First builds can take several minutes. An idle workspace suspends and can resume within its session window. An expired session needs a new build; startup time depends on the repository and services.
Security
Private code, an AI with write access, and a designer at the keyboard
All three are true at once, so the boring answers matter more than the clever ones.
Isolation by default
Previews run on separate machines with allocated CPU, memory and disk. Sessions have a one-hour compute window and temporary disks expire after 24 hours. Saved editor changes stay in the change history. Outbound network access is currently available; this is not a network-restricted environment.
Use test services and credentials
Revise prepares a separate preview with temporary services where supported. Use test data and sandbox credentials when a repository needs an external service. Developers should review configuration before connecting; do not supply production database credentials.
Credentials, if any, encrypted
When a repository needs credentials, a developer can provide them through a setup link. Stored secrets are encrypted and hidden from normal editor responses. Preview code may still use those credentials at runtime, so use dedicated test credentials with limited access.
Bounded scope
“Make checkout simpler” must not quietly touch your schema. Developers mark which paths are off-limits, and an attempt to edit one becomes a request they can approve rather than a change they have to catch in review.
Revibot
Someone has to say “that's getting big”
A branch that lives for days is fine for an engineer and a trap for everyone else. Revibot watches what's piling up and speaks up — in the words your team actually uses. It will never tell a designer to commit, because a designer has no idea what that means.
You've made 214 changes across 6 files. Want to send this to Dan for review before it grows?
Send for reviewbilling.ts is part of how the site works rather than how it looks, so Dan needs to make that change. Want me to ask?
Ask DanThe shared version of this project has moved on quite a bit since you started. Want me to bring your copy up to date?
Catch me upSarah is working on Hero.tsx right now too.
Why it matters
The failure mode of visual editing tools is not a bad edit. It is three weeks of unreviewed changes landing on an engineer at once, with no explanation of what any of it was for.
Small, explained, frequent pull requests are what make this workable — and the person making the changes needs a nudge to produce them, in language that means something to them.