Honeyvid
Put anyone in a viral AI video, or generate with Kling, Veo and more, straight from your agent.
Use HoneyVid from Claude Code, Codex, Cursor, shell scripts, or another agent. Create from a template or use Playground video and image models with your own prompt, settings, and reference photos. Generation uses account credits and usually takes 2–10 minutes.
Node.js 20 or newer. Plain ESM, no build step, no runtime dependencies. Published on npm as honeyvid:
npx honeyvid --help
# Or install globally:
npm install -g honeyvid
honeyvid --help
honeyvid schema
Prefer a remote MCP connection instead? Add https://honeyvid.ai/mcp (Streamable HTTP, OAuth, no API key) to your MCP client. Setup for every app: https://honeyvid.ai/mcp
Claude Code users can install the HoneyVid plugin (MCP server plus skills) from HoneyVid/skills: /plugin marketplace add HoneyVid/skills, then /plugin install honeyvid@honeyvid.
Sign in
honeyvid login
honeyvid whoami
Login prints a URL and an eight-character code, such as HVQK-7M2P, and opens the system browser when available. Check the code on HoneyVid matches your terminal, then click Connect. The browser shows Connected with the same code. The CLI finishes by itself and prints your account. No copy-paste or local listener is needed. Login lasts 10 minutes and uses PKCE S256 with no client secret.
For an agent, SSH, or a machine without a browser:
honeyvid login --no-browser
# Open data.url on any browser, check data.code, and click Connect.
# Leave the command running; it finishes after approval.
Piped output and --json print a JSON envelope immediately with {url, code, expiresInSeconds: 600, next: "Open the url and click Connect. Check the code matches."}, then a second envelope with the account after approval. In a terminal, the URL and code go to stderr. The CLI polls every two seconds. --no-browser skips opening the browser and still waits.
If the process stops, resume the same saved login within its original 10 minutes:
honeyvid login --wait
Use the same config directory and base URL. The saved verifier and state stay private in the local auth file; approval requires the verifier to exchange the code. login --code '<long-oauth-code>' remains as a legacy fallback for one release if you already copied an OAuth code. The new browser page shows only the short matching code, which is not an OAuth code.
Tokens are stored per base URL at ${XDG_CONFIG_HOME:-~/.config}/honeyvid/auth.json (file 0600, directory 0700). Expiring tokens refresh before requests; a 401 refreshes once and replays the request once. Rotated refresh tokens are saved atomically. A config lock serializes refreshes and writes so parallel commands share the latest rotating token. Queued jobs are exposed as processing.
honeyvid auth export --json
honeyvid logout
auth export returns data.refreshToken and warns on stderr. Treat it as a secret. HONEYVID_TOKEN supplies a refresh token for CI and overrides the local login. Its rotated credentials are cached separately, so later commands on the same machine use the new token without replacing the interactive login. Export the current token when moving CI to another machine. Never put tokens in source control, shared logs, or prompts. Logout removes local credentials for the selected base URL; it does not revoke a token or unset HONEYVID_TOKEN.
Template flow
honeyvid templates --search dance --limit 10 --json
honeyvid template '<template-id>'
honeyvid characters add ./face.jpg --name Alex
# Or:
honeyvid characters add --url 'https://example.com/face.jpg' --name Alex
honeyvid characters
honeyvid quote --template '<template-id>' --quality standard
honeyvid create --template '<template-id>' --character '<character-id>' \
--quality standard --max-credits 50 --idempotency-key 'my-video-001' \
--wait --timeout 600 --output ./video.mp4
From the project's README.