VibeKit logo VibeKit Enter App

VibeKit CLI

Terminal client for the VibeKit task + schedule API. Dispatch a coding task at a linked remote agent, schedule recurring cron-style jobs, check status — all from your shell. Built to compose with the rest of your dev environment.

Install

npm install -g vibekit-cli
vibekit auth

Latest published version: [email protected]. auth opens a browser OAuth flow and saves a token locally.

Commands

vibekit auth
OAuth sign-in. Stores a token in your user config directory.
vibekit account
Show the account you're signed in as + your plan.
vibekit task "<prompt>"
Send a coding task to a remote-linked agent. Returns a task ID immediately.
vibekit status <id>
Check status of a previously-submitted task.
vibekit wait <id>
Block until the task completes (or fails). Useful for shell pipelines.
vibekit tasks
List your active and recent tasks.
vibekit schedule "<prompt>" "<cron>"
Schedule a recurring task. Standard 5-field cron syntax.
vibekit schedules
List your scheduled tasks.
vibekit unschedule <id>
Cancel a scheduled task.

Useful patterns

Fire-and-wait from a shell script

id=$(vibekit task "rebuild the staging deploy snapshot for repo X" --json | jq -r .id)
vibekit wait "$id"
echo "done — see vibekit status $id for output"

Nightly cleanup via cron

vibekit schedule "delete stale branches from origin merged > 30 days ago" "0 4 * * *"

CI integration

# In a GitHub Action, after a PR merges, kick off a follow-up task on your dev box
- run: vibekit task "regenerate the SDK from openapi.yaml and commit"
  env:
    VIBEKIT_TOKEN: ${{ secrets.VIBEKIT_TOKEN }}

How this fits with the other packages

The CLI's sweet spot is shell-driven automation: scripts, cron, CI pipelines. The MCP server's sweet spot is in-editor agent workflows. Both call the same underlying API.

Drive your agents from your shell
npm i -g vibekit-cli · vibekit auth · vibekit task "fix the 500 on /api/users"
Get an API token →