viberaven 1.2.1 → 1.2.3

package/README.md

@@ -4,31 +4,42 @@
 [![npm downloads](https://img.shields.io/npm/dw/viberaven)](https://www.npmjs.com/package/viberaven)
 [![GitHub stars](https://img.shields.io/github/stars/ohad6k/VibeRaven?style=social)](https://github.com/ohad6k/VibeRaven/stargazers)
 
-AI got your app to demo. VibeRaven gets it to production.
-
-Open the local launch console from any app repo:
+**VibeRaven Studio** — open-source localhost workspace for production-aware AI coding.
 
 ```bash
 npx -y viberaven
 ```
 
-For the deeper non-interactive agent/pro gate:
+Run it inside any project folder. It opens a local console — no VibeRaven account, no API key. You connect the coding CLI you already use (Codex, Claude Code, or Gemini) and chat with your repo.
+
+## What you get
+
+- **Agentic chat** — missions that can read and edit files in your project (not just advice).
+- **CLI connect** — install, sign in, then **Test connection** before chat works.
+- **Permission modes** — ask before each change, or full access when you trust the run.
+- **Provider & release context** — drag Supabase, Vercel, Stripe, and version context into chat.
+- **Split chats** — separate threads for auth, billing, or deploy debugging.
+
+## Quick start
 
 ```bash
-npx -y viberaven --agent-mode
+cd your-app
+npx -y viberaven
 ```
 
-VibeRaven checks launch-readiness evidence for AI-built apps: Supabase RLS, Vercel config, env vars, auth redirects, webhooks, payments, monitoring, tests, and deploy readiness. It writes `.viberaven/` artifacts so coding agents can fix one launch gap, verify, and continue until the gate clears or a provider/user action remains.
+1. Open the **Terminal** tab and pick Codex, Claude, or Gemini.
+2. **Run sign in** if needed, complete login, then click **Test connection**.
+3. Switch to **Chat** and send your first mission.
 
-Public repo:
+## Links
 
-https://github.com/ohad6k/VibeRaven
+- Public repo: https://github.com/ohad6k/VibeRaven
+- Site: https://viberaven.dev
+- Feedback: https://github.com/ohad6k/VibeRaven/discussions/7
 
-If VibeRaven helps, star the repo so more AI app builders find the production gate. Use Watch -> Custom -> Releases for release notifications.
+If VibeRaven helps your launch workflow, star the repo on GitHub.
 
-Useful links:
+## MCP & agent gate (optional)
 
-- Launch discussion: https://github.com/ohad6k/VibeRaven/discussions/2
-- Feedback discussion: https://github.com/ohad6k/VibeRaven/discussions/7
-- Contributing guide: https://github.com/ohad6k/VibeRaven/blob/main/CONTRIBUTING.md
-- Full agent reference: https://viberaven.dev/llms-full.txt
+- MCP server: `@viberaven/mcp` on npm
+- CI / agent production gate: `npx -y viberaven --agent-mode` — see [@viberaven/cli](https://www.npmjs.com/package/@viberaven/cli) for artifact paths

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "viberaven",
-  "version": "1.2.1",
-  "description": "AI got your app to demo. VibeRaven gets it to production. Run `npx viberaven` for the local launch console.",
+  "version": "1.2.3",
+  "description": "VibeRaven Studio — open-source localhost console. Run `npx -y viberaven` to chat with your Codex, Claude, or Gemini CLI.",
   "license": "MIT",
   "author": "VibeRaven",
   "homepage": "https://viberaven.dev",
@@ -39,7 +39,7 @@
     "bin"
   ],
   "dependencies": {
-    "@viberaven/cli": "1.2.1"
+    "@viberaven/cli": "1.2.3"
   },
   "engines": {
     "node": ">=20"