Make a change and check it
Ask your coding agent for one small change, then check the result before you keep it.
Before you start
- Your computer is connected and you are on the app overview. See Connect your app.
- Your coding agent is signed in on that computer.
Steps
- Select "Start working" from the 2D overview to open the full-window 3D work view and the change panel. If the next step recommends a fix, its request is filled in for you to read and edit. If a change is already running, use "Open the work view" to follow it.
- Under "What should change in [your app]?", describe one small change in plain words, such as a heading text. Keep it to one change you can review. The box takes up to 1,200 characters.
- Choose a mode. "Edit": the agent changes files in your project. "Ask": the agent only says what it would change.
- Choose your agent: Claude Code, Codex or Gemini. Before each change VibeRaven runs a quick test that the agent is installed and signed in on this computer.
- Select "Make the change" (or "Get a plan" in Ask mode). The steps show as they run: read the project, the agent makes the change, run your checks, update the preview.
- Read the checks. Types runs your typecheck script (or tsc --noEmit), Tests runs your test script, and Page loads checks that the preview still answers. Anything that was not checked is listed under "Not checked".
- Select "Review" to read the diff. Look for files outside the change you asked for.
- Open the preview if it shows ("Live on your computer") and try the changed behavior yourself.
- Select "Overview" to return to the service map and "Readiness". This does not stop a running change. Escape also goes back, except while focus is in a text field containing text. Use "New change" in the work view for your next request.
What you should see
- A finished change with its checks, the changed files and a diff you have read.
- Nothing is deployed. The change stays in your local folder until you commit and deploy it yourself.
If it does not work
- "This app has no typecheck or test script, so nothing was checked.": The change ran, but no check covered it. Test the behavior in the preview yourself, or add a typecheck or test script to package.json.
- A check failed: Read the failing check, then ask for a fix in a new request, or select Undo if it is available for that Claude Code change.
- "[agent] is not ready on this computer": Open a terminal on that computer, start the agent's CLI and sign in, then send the request again.
- "You used your 2 free changes. Upgrade to Pro to keep going.": Free accounts get 2 changes. Pro is $20 a month for 300 changes. Ask mode does not use a change, but it needs one left to start.
Stop, Undo and Review
Undo works from the computer that made the change. If you made it on another computer, VibeRaven has no record of it there and cannot undo it.
Undo is available for changes made with Claude Code. VibeRaven knows which files are the agent's own edits by reading Claude Code's record of the edits it applied. It does not read that record for Codex or Gemini yet, so for those agents no file is attributed and Undo stays off: put files back yourself, for example with git.
| Control | What it does |
|---|---|
| Stop | Stops the agent. Files it already changed stay changed. Stop does not undo anything. |
| Undo | Puts back only the files proven to be the agent's own edits in that change. Other changed files are left alone. Select it twice: "Undo", then "Sure? Undo". |
| Review | Shows the diff of the change. "Hide the change" closes it. |
What uses a change
An Edit request reserves one change while it runs. When it finishes, it counts if the result reports at least one changed file, including files whose edits could not be attributed to the agent. A finished run with no changed files releases that change. Ask mode does not use a change in the end, but it holds one while it runs, so it needs a change left to start. A free account has 2 changes; Pro has 300 a month. Current plans are on viberaven.dev/pricing.
The website offers Edit and Ask. Full access is available only in the local Studio. Its prompt asks the agent to explain destructive actions, but that instruction is not a confirmation gate or a guarantee that the agent will pause.
Next
Checked
Checked on October 15, 2026, by reading the website code through PR #50 and VibeRaven CLI 1.6.10. Website revisions are separate from CLI releases. Not a recorded end-to-end run.
VibeRaven is built for apps on Vercel + Supabase. Its checks are advice, not a gate: you decide what to ship. They read your repository and run your project's own scripts, so they are a repository check, not a live database or security test.