@viberaven/cli
VibeRaven Studio — local-first open-source console for AI-built apps. Chat with your connected coding CLI, attach provider and release context, and work from localhost.
Public repo: https://github.com/ohad6k/VibeRaven
Run Studio
npx -y viberavenOpens VibeRaven Studio on localhost in the current project:
- Connect Codex CLI, Claude Code, or Gemini CLI (your existing CLI account — no OpenAI API key in VibeRaven).
- Terminal tab: install → sign in → Test connection (chat only works after verify).
- Chat tab: scoped missions that can edit the repo (permission mode: ask each change or full access).
- Provider Control Board and Versions & Releases context for drag-to-chat.
Explicit UI command:
npx -y viberaven ui .Install agent rules (optional)
npx -y viberaven init --agents allPreview without writing files: npx -y viberaven init --agents all --dry-run
Agent production gate (CI & coding agents)
VibeRaven is also the Agent Context + Production Gate for pre-deploy checks. Use this path when an agent or CI job needs repo evidence, not the Studio UI.
npx -y viberaven --agent-modeRead artifacts in order:
.viberaven/agent-tasklist.md.viberaven/gate-result.json.viberaven/context-map.json
Fix one repo-code gap, then:
npx -y viberaven --verify
npx -y viberaven --strictFocused helpers: npx -y viberaven next --json, npx -y viberaven prompt --gap <id>, npx -y viberaven audit --vercel-supabase
Chat-native actions
npx -y viberaven actions
npx -y viberaven verify --action VR-A1Writes .viberaven/actions.json as the action surface contract. Provider dashboard steps are not cleared by repo edits alone.
Machine output
npx -y viberaven --agent-mode --json
npx -y viberaven --strict --jsonArtifact schemas: docs/contracts/artifacts.md, https://viberaven.dev/schemas/gate-result.schema.json, https://viberaven.dev/schemas/context-map.schema.json, https://viberaven.dev/schemas/gap.schema.json, https://viberaven.dev/schemas/heal-result.schema.json
Development
npm run build
npm testLicense
MIT