Quickstart: install and upload your first video

beta

Install the agent-video CLI, sign in with your Agentics account, and upload a video from the terminal or wire an agent to do it for you.

Usage: agent-video login && agent-video upload session.mp4
Category: agents

Quickstart: install and upload your first video

Get from a fresh machine to an uploaded video in a few minutes: install the CLI, sign in, and run your first upload.

This guide gets you to a working setup. For full command and flag detail, see the CLI reference.

1. Prerequisites

  • An Agentics account — used for the OIDC sign-in in step 3.
  • A browser on the machine you're signing in from (the login flow opens one). Running somewhere headless? Skip straight to machine tokens below.

2. Install the CLI

The one-line installer detects your OS/architecture, verifies the checksum, and puts agent-video on your PATH.

Linux / macOS

curl -fsSL https://agentics.dk/install/agent-video.sh | bash

Windows (PowerShell)

irm https://agentics.dk/install/agent-video.ps1 | iex

Confirm the install:

agent-video version

You should see agent-video <version> printed.

3. Sign in

agent-video login

This opens your browser and runs an OIDC loopback flow against login.agentics.dk/realms/agentics. On success the CLI stores a refresh token (plus your sub and display name) in ~/.agent-video, then sanity-checks it with a GET to the videos list.

No token is written into any project file — every command auths from this stored login and refreshes silently.

4. Upload a video

agent-video upload session.mp4 --title "Sprint demo" --tag demo

The upload is chunked (8 MiB chunks) and shows a progress line while it runs. If it's interrupted — network drop, laptop sleep, whatever — just re-run the same command: the CLI resumes from the last chunk the server actually received instead of starting over.

agent-video upload session.mp4 --privacy password --password "letmein"
agent-video upload session.mp4 --wait   # block until server-side processing finishes

5. List and inspect

agent-video list
agent-video show <ID>

6. Wire an agent (optional)

If you want a coding agent to publish videos with no shell access, wire the stdio MCP server into the current repo's ./.mcp.json:

agent-video install

This writes an agent-video entry that runs agent-video mcp. No secret lands in the file — the MCP server auths from your stored login exactly like the CLI does. The agent then gets upload, list, and show as tools — see the MCP tools reference.

Machine tokens (CI / headless agents)

For a runner that can't open a browser, mint a machine bearer token once from a machine that can:

agent-video token mint --label "CI runner"

Then export it wherever the upload actually runs:

AGENT_VIDEO_TOKEN=<token> agent-video upload session.mp4

AGENT_VIDEO_TOKEN short-circuits OIDC entirely — every command (including agent-video mcp) picks it up automatically when set. Revoke it later with agent-video token revoke <ID>.

Next steps