CLI
The CLI sets up a project from inside your app's folder and checks the integration locally. It has no dependencies and runs on Node 20 or newer.
The CLI is not published to npm yet. Until it is, run it from the repository with pnpm vibeadmin init (it works on the folder you run it from, so pass --url for a local server). The commands below are what npx vibeadmin will run.
vibeadmin init
npx vibeadmin init ✓ Detected Next.js ✓ Detected Supabase Open https://www.easy-admin.solutions/device and enter the code: ABCD-1234 ✓ Signed in as you@example.com ✓ Created project "my-app" ✓ Created a development API key Added to .env.local: VIBEADMIN_API_KEY=adm_test_...
- Detects your framework and whether you use Supabase, Firebase or Clerk by reading package.json.
- Signs you in with a browser approval code, so no password or token is typed into the terminal.
- Creates a project and a development API key limited to users.read, users.write, events.write and analytics.read, and writes it to .env.local (mode 600). It warns if .env.local is not git-ignored.
- If it finds Supabase credentials in your env files, it offers to connect Supabase. Your service-role key is sent to VibeAdmin only if you say yes, and the connection is read-only.
- Prints the next steps for your stack. It never edits your source code.
vibeadmin dev
npx vibeadmin dev ✓ API key accepted (development) ✓ Test user created ✓ Test event recorded Your integration works.
Reads VIBEADMIN_API_KEY from your environment or .env files, creates a clearly named probe user and event, confirms they were received, and removes the user again if the key is allowed to delete users (the key made by init is not, so the single probe user stays and is simply updated on the next run). It refuses to run against a production (adm_live_) key.
Options
--url <origin> VibeAdmin server (default: https://www.easy-admin.solutions, or VIBEADMIN_URL) --yes accept defaults without prompting (init) --no-env print the key instead of writing .env.local (init) --help show help