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 authLatest published version: [email protected]. auth opens a browser OAuth flow and saves a token locally.
Commands
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
- vibekit-agent on your laptop = the worker that executes tasks dispatched by the CLI
- vibekit-cli on any machine (or in CI) = the dispatcher
- vibekit-mcp = the same dispatcher, but exposed as MCP tools so Claude Desktop / Cursor can call it directly
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.
FAQ
What does vibekit-cli do?
It's a terminal client for the VibeKit task + schedule API. You can fire off a coding task at a linked remote agent ('refactor the auth module on machine X'), wait for it to complete, check status, or schedule it to run on a cron. Useful for automating agent workflows that don't fit into the iOS or web UI.
Does it deploy hosted apps?
For hosted-app lifecycle (create, deploy from GitHub, restart, env vars), use the MCP server or the REST API directly. The CLI is focused on task dispatch and scheduling against remote-linked agents. The two systems overlap but the CLI's sweet spot is shell-driven automation.
How do I authenticate?
Run `vibekit auth`. It opens your browser to OAuth into VibeKit and writes a token to your shell's config directory. Subsequent commands use that token until you log out.
Does this replace vibekit-agent?
No — they pair. `vibekit-agent` runs on your laptop to be a remotely-controllable worker. `vibekit-cli` is what you'd run on a *different* machine (or even the same one) to dispatch tasks at it. Common pattern: agent on dev laptop, CLI on a build server, scheduled tasks fire from the build server at the dev laptop.