VibeRaven docs
VibeRaven works on an app you already have. Add it, read its service map, and connect the computer that holds the app. Choose Start working to ask your coding agent for a change from the website, then review what changed with the checks next to it. These pages cover each step and what to do when one fails.
Connect your app to VibeRaven
Add your app on viberaven.dev and connect the computer that holds it, so your coding agent can make changes there from the website.
Add your app on viberaven.dev, sign in with Google, then connect the computer that holds it with one command. Needs Node.js 20+ and a signed-in agent.
Make a change and check it
Ask your coding agent for one small change, then check the result before you keep it.
Ask your coding agent for one small change from viberaven.dev, read the checks and the diff, then try the result. What Stop and Undo actually do.
Understand your app's services in VibeRaven
Read what VibeRaven knows about the services your app uses, and know which questions it does not answer.
What VibeRaven shows about your database, hosting and payments: what was found in your code, what you chose, and why neither proves a live connection works.
Fix common VibeRaven problems
Find the message you see and the fix for it.
What to do when your computer will not connect, your coding agent is not ready, the preview does not load or VibeRaven says your version is too old.
The local Studio
Prefer to stay in your terminal? Run npx -y viberaven in your app folder to open the local Studio on your computer. It needs no account. The guides below describe the website flow.
Scope
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.
Problem guides
Guides for errors in your app, such as Vercel environment variables or Supabase row level security, are on the guides page.