video2ctx Monitoring

Use the installed video2ctx CLI for authenticated requests to https://api.video2ctx.dev.

Check the CLI

Run video2ctx --version. When the command is unavailable, explain that this hosted skill requires the public @video2ctx/cli npm package and ask the user to approve its installation. After approval, run:

npm install --global @video2ctx/cli

Confirm video2ctx --version succeeds before continuing. Use that installed command for every request so authentication and versioning stay stable.

Authenticate

Run video2ctx whoami --json. When it reports AUTHENTICATION_REQUIRED, run video2ctx auth login. Relay the displayed URL and code if the user must continue in a browser, use --no-browser only when opening a browser is unavailable, and then retry video2ctx whoami --json. Do not run auth status first; both identity commands resolve the same remote account.

The login flow stores a revocable CLI session in the user's local config with private file permissions. Keep the session out of prompts, logs, screenshots, and source control. The CLI also accepts VIDEO2CTX_API_KEY as a non-interactive fallback and gives it precedence over the stored session. Have the user create and configure a personal key at https://video2ctx.dev/dashboard/developer when they prefer that mode; never ask them to paste it into the conversation.