Ask for a change from the dashboard, with no laptop setup and no terminal. Revyse works on a safe copy of your repository, runs your checks and the build, opens a pull request and checks your preview. Then the change ships the way your project chose.
You need
- A project on Revyse, with credits.
npx revyse initcreates one, and connects your GitHub repository and Vercel project too. - The Revyse GitHub App installed on the GitHub account or organization that owns the repository (organization → Integrations → GitHub → Install). Revyse asks GitHub for the least it needs: repository contents and pull requests (read and write), metadata and checks (read). Nothing more.
- Optional: the Revyse Vercel integration on the Vercel account or team that deploys the repository (organization → Integrations → Vercel → Install), for previews.
revyse.config.jsoncommitted on the base branch.npx revyse initwrites it; commit it once.- With
"engine": "agent"inrevyse.config.json, cloud changes run the coding agent: it can create and delete files, and its pull request carries all of them.
1. Connect the project
If init connected your repository and Vercel project, skip this. Otherwise, in the
project's Settings: Repository → choose the repository and the base branch (the
default branch unless you say otherwise). Both are checked on GitHub. Then Previews →
choose the Vercel project that deploys it.
2. Ask for a change
On the project's Changes tab, press Request a change. Say what you want, in words. Add the page it's about (its address) and a screenshot if you like. Revyse copies the repository at the base branch, finds the files from the page's route and the words you quoted, and plans.
3. Apply the plan
The plan appears on the change page with its steps. Apply the plan runs it on a fresh copy at the same commit: the change, your checks (typecheck, lint, tests) and the build, each with its evidence. Then Revyse commits the change as you, pushes it to its own branch and opens a pull request with the request, the plan, the files and the checks.
4. See the preview
When Vercel's preview for the commit is ready, its link appears on the change page and on the pull request, with the result of Revyse loading it in a browser. If the build fails, both say so.
5. Ship it
Each project chooses how its changes ship. Owners set it in Settings → Release:
- Preview, then promote (new projects): someone the project allows opens the preview and presses Promote to production on the change page. Owners choose who may promote: anyone who can ask for changes, or only approvers and owners.
- Straight to production: when the checks show nothing newly broken, Revyse ships the change by itself. A change that breaks a check never ships by itself.
- Review: an approver approves or rejects on the change page. When the project names reviewers, only they decide, in Revyse or by approving the pull request on GitHub. A person merges the pull request on GitHub.
Under the first two, Revyse merges the pull request and your host deploys it. Revyse merges only the commit that was decided on: if someone pushed to the branch since, it stops and says so. If GitHub refuses the merge (a branch rule, say), the change page says why, with Try the merge again.
Costs
Each change is charged to your organization's credits for the AI it used and the checks and build it ran. The cost is on every change, whether it ships or fails. Owners can cap a project's spend for every 30 days, and pause it at once.