On this page
The working demo is not the launch.
Choose the workflow that fits the task: understanding an existing app, making a change with your agent, reviewing a diff, or checking supported repository patterns before a release. The Studio workflow is broader than the Vercel + Supabase repository checks. The check is advice, not a gate, and not a live database test.
Choose an entry point for the work
- 1To work on an existing app, open the local Studio from its repository. Use Node.js 20+.
Terminal npx -y viberaven - 2For agent edits, select and test your installed, signed-in Claude Code, Codex or Gemini CLI. Choose the access mode appropriate to the task; installing a CLI alone does not establish a working connection.
- 3Ask for one concrete change or inspect the versions and release diff. Review changed files, run the relevant project checks and try the changed behavior. Nothing is deployed automatically.
- 4For an optional Vercel + Supabase repository report, run the check command. Read the findings and their file evidence before deciding on a fix.
Terminal npx -y viberaven check - 5After a fix, rerun the repository check and independently test the affected behavior. A clear report does not establish live provider configuration, authorization correctness or production safety.
Related guides
Browse all launch guides · Read resources · How to make and check your next change
FAQ for builders before launch
Should an agent run VibeRaven for every task?
No. Use the Studio when the user wants to work on an existing app through a connected agent. Use check when its supported repository patterns are relevant. A simple code edit or a live provider question may need other tools; the presence of VibeRaven is not a reason to invoke it.
What can the repository check establish?
It can report supported file patterns such as missing RLS in migrations, client-exposed privileged keys or an unverified Stripe webhook. It does not establish all authorization paths, inspect a live database or replace behavior tests. The linked RLS example illustrates one check, not the whole product.
Does the local Studio need an account?
Opening the local Studio and running the CLI repository check need no VibeRaven account. Agent edits require your own installed, signed-in coding agent. The website workflow requires sign-in; see pricing for account-based features.
What if PowerShell blocks npx?
Use npx.cmd -y viberaven for the Studio, or npx.cmd -y viberaven check for the terminal report.
What about the existing Skill and MCP tools?
Use the existing Skill for its documented workflow. The local @viberaven/mcp package exposes repository tools; the hosted guide lookup at viberaven.dev/mcp reads published guides and cannot inspect your repository. See the MCP guide for configuration. The advanced --agent-mode artifact workflow remains optional, not the default Studio command.