For Developers Claude Code, Codex, and terminal-first workflows

Build Videos With Claude Code or Codex.
Render Them With SlideVids CLI.

Use Claude Code or Codex to generate structured SlideVids timelines, then run predictable CLI commands to create, render, wait, and download the final video. No UI required for the happy path.

  • ✓ Generate timeline.json with Claude Code or Codex
  • ✓ Create, render, wait, and download with explicit CLI commands
  • ✓ --json output for scripts, integrations, and CI
  • ✓ Built on the SlideVids public API
Upgrade to Pro Read CLI Docs
CLI access is available on Pro and Max. Pro fits most developer workflows. Max is the better choice for heavier automation, higher throughput, and more concurrent renders.

Prompt -> File -> Render

Prompt

Use the SlideVids CLI for this workflow.
1. Create timeline.json for a 6-slide product explainer.
2. Create the timeline from that file.
3. Start a render, wait, and download the output.
4. Return IDs and the final output path.

timeline.json

{
  "title": "Agent-ready demo",
  "slides": [
    { "title": "Problem", "speakerNotes": "..." },
    { "title": "Workflow", "speakerNotes": "..." }
  ]
}

Execution

$ slidevids timelines create --file ./timeline.json --json
$ slidevids renders create --timeline-id <timeline_id> --no-wait --json
$ slidevids renders wait <render_id> --interval 3 --timeout 900 --json
$ slidevids renders download <render_id> --output ./artifacts/final.mp4

Output

./artifacts/final.mp4

Surface

Built on the public API

Fit

Scripts, CI, integrations

The Problem

Most creative tools still break when an agent touches them.

Developers are doing real production work with AI agents now: generating files, running commands, assembling assets, and shipping outputs from the terminal. But most creative tools still assume a human clicking around a UI. That creates brittle workflows, fuzzy handoffs, and too many manual steps between prompt and finished asset.

Traditional Video Production
The Reality
UI-only creative workflows
Hard to automate and repeat
Prompt-only execution
Too ambiguous for reliable output
Unstructured command surfaces
Agents guess and break
Non-parseable output
Poor fit for scripts and CI
Manual handoff from draft to render
Slow and error-prone
"Your agent handles the flexible thinking. SlideVids CLI handles the exact steps."
Terminal Workflow

A Clean Path From Prompt to MP4

The workflow is simple on purpose. Let the agent draft the content. Let the CLI execute the deterministic parts. Because the CLI is built on the SlideVids public API, the same flow also fits scripts, integrations, and CI.

Recommended path: Claude Code or Codex -> `timeline.json` -> `slidevids` -> final `.mp4`

Real Workflows

Built for Repeatable
AI-Assisted Production

Use Case 1

A Product Explainer Draft in One Terminal Session

The Situation

You have a product brief, a target audience, and a rough idea of the story. What you do not want is to start from a blank UI and hand-build every first draft before you even know whether the structure works.

With SlideVids:

  1. 1Ask Claude Code or Codex to draft a short explainer as timeline.json
  2. 2Create the timeline from file with slidevids timelines create --file
  3. 3Start a render, wait for completion, and download the result
  4. 4Review the first cut and iterate from a structured file

Time Comparison:

Approach
Timeline
Cost
UI-first draft
Manual setup before first render
High friction
SlideVids CLI
Prompt -> file -> render
Deterministic workflow

Your first video draft comes from a prompt plus a clean command sequence, not a slow manual setup process.

Use Case 2

Recurring Internal Updates Without Rebuilding the Workflow

The Situation

You keep producing the same kinds of videos: launch updates, onboarding clips, internal explainers, enablement content. The details change, but the workflow shape stays the same.

With SlideVids:

  1. 1Keep the structure in files instead of rebuilding in the UI
  2. 2Reuse project defaults through slidevids.toml
  3. 3Generate fresh timelines from repeatable prompts
  4. 4Run the same create, wait, and download path each time

Result: Repeatable output without inventing a new process for every video.

Use Case 3

Built for Scripts, Not Just Demos

The Situation

You want the workflow to survive past local experimentation and fit scripts, CI jobs, or more operational automation where machine-readable output and explicit state transitions matter.

With SlideVids:

  1. 1Authenticate with environment variables or API keys
  2. 2Use --json for parseable output
  3. 3Keep create, wait, and download as explicit steps
  4. 4Persist IDs and output paths for downstream jobs

The CLI is built on the SlideVids public API, so the same workflow fits local terminal use, integrations, and CI.

Use Case 4

Agency and Ops Handoffs That Stay Clean

The Situation

An agent can draft structure, images, and narration, but you still need a dependable way to turn that into a real deliverable other people can review, debug, or build on.

With SlideVids:

  1. 1Prepare structured content with an agent
  2. 2Use the CLI as the deterministic execution layer
  3. 3Return timeline IDs, render IDs, and file paths cleanly
  4. 4Hand off a real output instead of an ambiguous chat transcript

Result: Better handoffs between creative planning and operational execution.
Why It Works

What Makes This
Agent-Friendly

SlideVids CLI gives AI agents and humans a predictable execution surface instead of a fragile creative workflow.

Explicit Command Groups

Auth, timelines, renders, templates, webhooks, and API keys are all separated cleanly so agents do less guessing.

File-Based Timeline Creation

slidevids timelines create --file is the bridge between agent-generated structure and real SlideVids timelines.

JSON Output for Automation

Use --json to keep results machine-readable for scripts, CI jobs, and tool-assisted execution.

Real API Foundation

The CLI is built on the SlideVids public API, which makes it a credible path for integrations rather than a dead-end wrapper.

Project Defaults

slidevids.toml keeps repeated render settings consistent across runs without repeating flags everywhere.

Short Happy Path

Create, wait, download. The core flow is simple enough for humans to follow and deterministic enough for agents to execute.
Docs and Resources

Everything You Need to Go Deeper

This page sells the workflow. The docs help you run it. Start with whichever one matches where you are.

CLI overview

See the full CLI landing page and supported workflow surface.

Install and auth

Install @slidevids/cli, log in, and verify your setup.

Command reference

Review the core command groups and flags.

Terminal workflows

See the standard create, wait, and download patterns.

Claude Code guide

Prompt patterns for explicit, reliable terminal execution.

Codex guide

Codex-oriented workflow templates and reliability notes.

API overview

Understand the public API the CLI is built on.

API authentication

Review API key and bearer-token authentication behavior.
Read the CLI launch post
Access and Pricing

Choose the Plan That Fits Your Workflow

CLI access is currently available on Pro and Max because the CLI uses the same public API surface. For most individual developers, founders, and small teams, Pro is the right starting point. Max is for heavier CI, higher-volume automation, and more concurrent rendering.

Recommended

Pro

Best for most Claude Code, Codex, and terminal-first users.

Default

Max

Best for higher throughput, more concurrent renders, and heavier operational usage.

  • •Trial and Starter do not include CLI access.
  • •Use Pro to start running the workflow immediately.
  • •Move to Max when your automation needs more headroom.
See Pro and Max View API docs
Compare Approaches

Why This Beats
UI-Only or Prompt-Only Workflows

Why the CLI + agent model is stronger

UI-only workflows are too manual for repeatable developer work. Prompt-only workflows are great for drafting but weak at exact execution. SlideVids gives you a better split of responsibility: the agent drafts and adapts the structure, while the CLI executes the deterministic steps to create, render, wait, and download.

UI-Only Workflow
Prompt-Only Workflow
SlideVids CLI + Agent
Manual setup for each draft
Good at drafting
Prompt-driven planning
Hard to automate
Ambiguous execution
Deterministic execution
Weak fit for CI
No clean render surface
Built for scripts and integrations
Slow handoff from idea to output
Hard to debug reliably
Clean path from file to `.mp4`
FAQ

Questions Developers
Actually Ask

From the Terminal

From Prompt to Rendered Video,
Without Leaving Your Terminal.

CLI access is available on Pro and Max. Start with the docs if you want the exact commands, or upgrade when you are ready to run the workflow in Claude Code, Codex, scripts, or CI.

Upgrade to Pro Read CLI install docs Compare Pro vs Max