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.
npx -y viberaven@1.7.8 checkRun it in your app folder first. The repository check is free and needs no account. Or ask your coding agent to "run npx -y viberaven check and fix what it reports".
Before you start
- A computer with your app's folder on it, checked out at the repository and branch you want to work on. VibeRaven runs your coding agent there, not in the cloud.
- Node.js 20 or newer on that computer. Check with
node -v. - One coding agent installed and signed in on that computer: Claude Code, Codex or Gemini CLI. Your agent uses your own account, and its usage is billed by its provider.
- A Google account to sign in to viberaven.dev.
- Use the computer that holds your app for this walkthrough. You can sign in and see your apps on a phone, but connecting still needs that computer, and a localhost preview opens on the device viewing it, not remotely on your phone.
Steps
- Open viberaven.dev/try and select "Continue with Google". You start free, with 2 changes and no card.
- Under "Connect your project", choose "Paste a GitHub link" and paste your app's repository, or "Connect GitHub" to pick one from your account, private ones included. Select "Continue". Nothing is cloned or changed.
- VibeRaven reads the repository and shows the services it found under "Your stack". Tap one to turn it off, or "Add" one it missed, then select "Continue". This reads GitHub; it does not connect your computer or verify that the services work live.
- The next step is "Connect this computer", with the line ready to copy. Select "Copy line" and run it in a terminal opened in your app's folder, or "Copy prompt for your agent" to hand it to your coding agent. The line has this shape, with your own session and one-time token:
npx -y viberaven connect --session <your session> --token <one-time token> - Keep that terminal open. VibeRaven can work on your app only while it runs. Press Ctrl+C to disconnect. Once it connects, the app opens on its page, a 2D overview of its services, saved under "Your apps".
- Once connected, the first local check starts automatically. Read the service map and "Readiness" results, then select "Start working" when you are ready to make a change. You can start while the local check runs; if it fails, the next action is "Run the check again".
What you should see
- The terminal prints "Connected. Your app page on viberaven.dev now shows this computer."
- Under "Readiness", the computer card says "Your computer is connected", and the first local check starts by itself.
- You stay on the overview until you select "Start working". That opens the full-window 3D work view with the change panel; it does not submit a change by itself.
If it does not work
- "That line expired. Get a new one.": Each line works once, for 10 minutes. Select "Connect this computer" again and run the new line.
- "That terminal was in a different project or branch.": Open the terminal in this app's folder, check out the branch the app page uses, then get a fresh line.
- The page goes back to "Not connected": The terminal running the connect line was closed or the computer went to sleep. Run a fresh line and keep the window open.
- npx fails before it connects: Check
node -v. VibeRaven needs Node.js 20 or newer.
What VibeRaven stores
The app page says it in its own words: "Requests, progress, check results, file paths and redacted, size-limited diffs are stored by VibeRaven. Redaction may miss confidential content." Your coding agent runs on your computer with your own account. Read the privacy policy at viberaven.dev/privacy for the full details.
The local Studio instead
Run npx -y viberaven in your app folder to open the Studio on your own computer, at a 127.0.0.1 address. It needs no account. The website flow above is for working on your app from viberaven.dev.
Next
Checked
Checked on October 15, 2026, by reading the website code through PR #50 and VibeRaven CLI 1.6.12; the CLI messages it quotes and its Node.js requirement were re-checked in the published VibeRaven CLI 1.7.8 on November 3, 2026. 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.