Help

Versie Help & Setup

Setup guides, shipping configuration, and more.

Setup

Claude Skill

No terminal — just Claude Code or Claude Desktop

Download SKILL zip file

Get the file from the Versie GitHub repo.

Skill Zip File →

Drop it in your project

Check the instructions for your tool:

Claude Code →Claude Desktop →

Say "versie setup"

Open Claude Code or Claude Desktop and say 'versie setup' to get started.

CLI + MCP

Any AI tool — Cursor, Windsurf, Claude, and more

Install

Run this once in your terminal — installs the versie command and configures your AI tool automatically.

npx versie-cli --install

Restart your AI tool and open a project

Open Cursor, Claude, Windsurf, or any supported tool and navigate to your project.

Say "set up versie"

Your AI tool sets up the project — creates your workspace, connects to GitHub. Say 'save my work' anytime after to see your project appear in the dashboard.

Optional

Connect to the dashboard

Run versie login and approve in the browser to sync your saves to a web dashboard. You can skip this and add it later anytime — the free CLI works fully without it.

versie login

ProPRO

Full dashboard with deploy tracking and rollback

Pro requires versie login — this connects your CLI to the dashboard so your projects, saves, and ships appear in your web view.

Install

Run this once in your terminal — installs the versie command and configures your AI tool automatically.

npx versie-cli --install

Connect to the dashboard

Run this in your terminal — approve in the browser so your saves sync from day one.

versie login

Restart your AI tool and open a project

Open Cursor, Claude, Windsurf, or any supported tool and navigate to your project.

Say "set up versie"

Your AI tool sets up the project — creates your workspace, connects to GitHub. Your live app won't change until you say 'ship it'.

Say "save my work"

Your first save syncs to the dashboard and your project appears.

Upgrade to Pro

Unlock the full timeline and deploy tracking.

Go to upgrade →

Shipping Setup

Configure your deploy platform so only "ship it" goes live, not every save.

Vercel

Good news! Vercel protects you by default. It only deploys from your live branch (main), so saving your work won't touch your live app.

Prerequisite

Make sure your Vercel project is connected to your GitHub repo. Go to vercel.com → your project → Settings → Git. If no repo is connected, click Connect Git Repository and select your repo.

Double-check your production branch

Open your project settings

Go to vercel.com → your project → Settings → Git

Check Production Branch

Under Production Branch, confirm it's set to main (or your live branch)

Preview builds on versie-dev are harmless — private previews only, no effect on your live app.

Optional — stop preview builds on versie-dev

This saves build minutes if you don't need preview deploys for your work branch.

Open Build and Deployment settings

Go to vercel.com → your project → Settings → Build and Deployment

Add an Ignored Build Step

Scroll to Ignored Build Step, select Custom, and paste:

if [ "$VERCEL_GIT_COMMIT_REF" == "versie-dev" ]; then exit 0; else exit 1; fi

Save

Click Save. Versie-dev pushes will no longer trigger builds.

Netlify

Tell Netlify to only go live from your live branch so saves stay private.

Open your site configuration

Go to netlify.com → your app → Project configuration → Build & deploy → Continuous Deployment → Branches and deploy contexts → Configure

Set the production branch

Make sure production branch is set to main

Restrict branch deploys

Under Branch deploys, choose Deploy only the production branch

After this, saving your work won't update your live app — only "ship it" will.

Railway

Point Railway to your live branch only so it doesn't go live on every save.

Open your service settings

Go to railway.app → your project → your service → Settings

Set the trigger branch

Under the GitHub integration section, set the trigger branch to main

After this, saving your work won't update your live app — only "ship it" will.

Render

Confirm Render is pointed to your live branch and auto-deploy is enabled.

Open your service settings

Go to render.com → your service → Settings → Build & Deploy

Check the connected branch

Confirm the connected branch is main

Ensure Auto-Deploy is on

Make sure Auto-Deploy is enabled so "ship it" triggers a live update automatically

After this, saving your work won't update your live service — only "ship it" will.

Supabase

Supabase migrations and edge functions don't ship automatically. You need a GitHub Actions workflow to run them when you say "ship it". Once set up, deploys appear in your Versie dashboard under deploy tracking.

Before you start

Run this once in your terminal to link the Supabase CLI to your project. Your project ref is in the URL: supabase.com/dashboard/project/<ref>

supabase link --project-ref <your-project-ref>

Make sure supabase/config.tomlis committed to your repo — GitHub Actions reads it to know which project to deploy to. It's not sensitive and should not be gitignored.

Add GitHub secrets

Go to github.com → your repo → Settings → Secrets and variables → Actions and add:

SUPABASE_ACCESS_TOKEN

Find at: supabase.com → Account → Access Tokens

SUPABASE_DB_PASSWORD

Find at: supabase.com → your project → Settings → Database → Database password (migrations only)

Migrations workflow

If you have a supabase/migrations/ folder, create this file in your project:

.github/workflows/supabase-migrations.yml

name: Supabase Migrations
on:
  push:
    branches:
      - main

jobs:
  migrate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: supabase/setup-cli@v1
        with:
          version: latest
      - run: supabase db push
        env:
          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
          SUPABASE_DB_PASSWORD: ${{ secrets.SUPABASE_DB_PASSWORD }}

Edge functions workflow

If you have a supabase/functions/ folder, create this file:

.github/workflows/supabase-functions.yml

name: Supabase Edge Functions
on:
  push:
    branches:
      - main

jobs:
  deploy-functions:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: supabase/setup-cli@v1
        with:
          version: latest
      - run: supabase functions deploy
        env:
          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}

If you have both migrations and edge functions, create both workflow files. They'll run in parallel when you ship.

Once set up, every time you say "ship it", your Supabase changes will deploy automatically alongside your frontend. The result will show in your Versie dashboard.

Still stuck? support@versie.co