Known limitations

What Revyse can't do yet, as of 3 November 2026. When one goes away, it comes off this page.

Your app

Next.js only, versions 14 to 16, on Node 22.12 or later. Revyse detects Vite and Create React App, but doesn't run in them yet.
One app per repository, at its root. Cloud changes read revyse.config.json from the top of the repository, so an app in a folder of a monorepo isn't supported yet.
The Pages Router needs a custom pages/_document.tsx (Next's default one is fine) for Revyse to load on your live site, and in development with Turbopack. A warning says so.

The agent engine is opt-in: add "engine": "agent" to revyse.config.json. Until it passes Revyse's evaluation suite, the default engine makes front-end changes to code you already have.
One new package at most, and only Resend's. Revyse adds a connected service's package by itself. A change that needs any other package says so, and you install it.
Email is the only service Revyse connects, through Resend, and it sets variables only on Vercel and Railway. Your other providers keep working as they are; you set their variables.
When Revyse can't tell which file draws what you selected (a component from a library, say), the default engine stops and asks you to select it again, or something near it. The agent engine searches your code instead.
Two changes planned on the same file at once conflict: plan the second again. To undo an earlier change after a later one edited the same file, undo it by hand.
Builds don't run on your machine (your dev server shows the change); they run on cloud changes. Typecheck and lint run right after each local change, in the background. Their results are on the change's page and in your dev server's output, not in Revyse's chat.
Lint covers just the changed files only when your lint script is plain eslint or eslint .. Otherwise it lints the whole project.
The browser check needs Chromium or Chrome on your machine. Without one, the check says "not run", never "passed".

Cloud changes need your GitHub repository connected, with revyse.config.json committed.
Revyse's safe copy is locked down. It reaches only GitHub, the npm and Yarn registries and Revyse. Installs follow your lockfile with install scripts off, and your app's own environment variables aren't there. A private registry, a postinstall step (like prisma generate) or a build that needs your variables can fail in the cloud.
Previews come from your own Vercel project. Without one, a cloud change has no preview and no browser check. Revyse-hosted previews for every project are on the way.
Protected Vercel previews show Vercel's login page to anyone outside your Vercel team.
From the dashboard, a cloud change can't be answered or revised: a question or a wrong plan means asking again. On your live site, you can answer and revise.
Dashboard requests have no element selection. Revyse works from the page's address and the words you quote. To select an element, ask on your live site or in your dev server.
Release settings apply to cloud changes. A local change is yours to commit.
Under Review, a person merges the pull request on GitHub. Branch rules on GitHub can refuse Revyse's merge; the change page says why.
Drafts are new. They group your changes, and with a repository connected your local changes go on the draft's branch. Cloud changes don't join drafts yet, and a draft has no pull request, preview or link to share yet.

Revyse opens only on the addresses you register. There are no wildcards, so it doesn't open on preview deployments, whose addresses change.
Without exact locations, Revyse finds the file from the page, so a style change to a shared component can land where it's used instead. npx revyse init turns exact locations on for sites on Vercel; elsewhere, set them up by hand.
Each person can ask for 30 changes an hour from the live site, and each site 120.

The Revyse team adds your credits. There are no card payments or top-ups yet.
Deleting an organization is done by hand: ask the Revyse team.
What changed and the checks' output are deleted after 90 days, screenshots after 30. The plan, the list of files and the verdicts stay.