New Types of Agents

Set up vidbyte-cli, the Vidbyte command-line tool, on this computer for me: from nothing to a working, logged-in install. Read this whole prompt first, then do the steps in order, one at a time. How to work with me - Run each step's read-only checks yourself before asking me anything; ask only what a command cannot tell you. - Before installing software, changing PATH or shell settings, or using sudo or admin rights, show me the exact command and wait for my yes. If your sandbox blocks network or file access, ask me to allow it or give me the command to run. - When a step fails, show me the exact error lines and what they mean, then try that step's fix. Never repeat a failing command unchanged, or call a step done before its check passes. - Written for vidbyte-cli 0.2.0, the current PyPI release. If a newer version differs, trust its `--help`. Three rules you never break 1. Keys stay out of this chat. Never ask me for my Vidbyte API key or any other key. If I paste one, tell me to revoke it at https://vidbyte.pro/settings/api/keys and create a new one. Never put a key in a command, file, environment variable, or your notes, and never print the value of VIDBYTE_API_KEY or OPENAI_API_KEY. 2. I type keys, not you. Never run `vidbyte-cli login` or `vidbyte-cli provider login` yourself, and never pipe a key into `--with-token`, even when an error hint suggests it. They need hidden typing at a real keyboard and hang or fail from your shell; I run them in my own terminal. 3. No spending without my yes. Before anything that can charge me (buying a plan, adding usage, starting a research run or an agent), tell me the cost and wait for my explicit yes. During setup never run `vidbyte-cli billing top-up` (a real payment), `vidbyte-cli research start`, `vidbyte-cli agents suggest run`, or any runtime launch. Step 1. Look before you change anything (you) Work out my operating system and shell (WSL counts as Linux), then run these and keep the output: - `vidbyte-cli --version` - Every copy on PATH: `which -a vidbyte-cli` (macOS, Linux, Git Bash) or `where.exe vidbyte-cli` (PowerShell or cmd). - If vidbyte-cli exists: `vidbyte-cli doctor` and `vidbyte-cli whoami`. - Python: `python3 --version`, `python --version`, and on Windows `py -0p`. - Installers: `pipx --version`, `python3 -m pipx --version` (Windows: `py -m pipx --version`), and `uv --version`. Tell me in a few lines what is done, then go to the first step that is not: - vidbyte-cli not found: Step 2. - `vidbyte-cli, version 0.2.0` or newer: Step 4. - An older version: upgrade it in Step 3 with the tool that installed it. - `whoami` printed `Authenticated as: ...`: Step 7. Step 2. Python 3.11 or newer (you check, I approve installs) Skip this step if Step 1 found Python 3.11+ or uv (uv can fetch its own Python). - Windows: `python` or `python3` may be a Microsoft Store shortcut that only prints "Python was not found"; trust `py -0p`. If no 3.11+ exists, offer `winget install -e --id Python.Python.3.12` or the https://www.python.org/downloads/ installer with "Add python.exe to PATH" ticked; then I open a new terminal. - macOS: the built-in python3 is often too old. Offer `brew install python@3.12` with Homebrew, otherwise the python.org installer. - Linux: use uv (Step 3, B). Step 3. Install vidbyte-cli (you, after my yes) pipx and uv give a command-line tool its own private folder, so it cannot break other Python programs, and put it on PATH. Choose by what Step 1 found: pipx installed, use A. No pipx but uv installed, use B. Neither: on Linux, install uv and use B (no sudo needed); on Windows or macOS, install pipx, then use A. Use C only if A and B fail. "pipx" below means however pipx runs here: `pipx`, `python3 -m pipx`, or on Windows `py -m pipx`. A. pipx. - Installing pipx: Windows `py -m pip install --user pipx` (its "not on PATH" warning is expected; keep using `py -m pipx`); macOS `brew install pipx`, or without Homebrew `python3 -m pip install --user pipx`. - First `pipx install vidbyte-cli`, then, after asking (it edits my PATH), `pipx ensurepath` run the same way as the install. - pipx picked a Python older than 3.11: `pipx install --python <path to python 3.11+> vidbyte-cli`. - "already seems to be installed": `pipx upgrade vidbyte-cli`. B. uv: `uv tool install vidbyte-cli` (add `--python 3.12` if my Python is older than 3.11), then, after asking, `uv tool update-shell` for PATH. To install uv (macOS or Linux, no sudo): `curl -LsSf https://astral.sh/uv/install.sh | env UV_NO_MODIFY_PATH=1 sh`, then run it as ~/.local/bin/uv until a new terminal. Run ensurepath or update-shell only once; "not on your PATH" warnings and `source ~/.bashrc` hints are expected (Step 4 covers them). C. A dedicated virtual environment (write my home folder in full; PowerShell does not expand ~): `<python 3.11+> -m venv <home>/.venvs/vidbyte-cli`, then `<home>/.venvs/vidbyte-cli/bin/python -m pip install vidbyte-cli`. The command is `<home>/.venvs/vidbyte-cli/bin/vidbyte-cli`; on Windows `Scripts/python.exe` and `Scripts/vidbyte-cli.exe` replace the `bin/` names. Never use `sudo pip`, `--break-system-packages`, or `pip install --user vidbyte-cli`. If the install fails: - "No matching distribution found for vidbyte-cli" with "Requires-Python >=3.11": that Python is too old; go back to Step 2. - "externally-managed-environment": this Python blocks pip outside a virtual environment; use B or C. - "ensurepip is not available" (C on Debian or Ubuntu): I install the python3-venv package it names with sudo, or use B. - A build error ("Failed building wheel", "Microsoft Visual C++ 14.0 or greater is required", "xcrun: error"): retry with 64-bit Python 3.11, 3.12, or 3.13. On an Intel Mac, first install the compiler with `xcode-select --install` (ask me). Step 4. Check the install (you) - `vidbyte-cli --version` must print `vidbyte-cli, version 0.2.0` or newer. - "command not found" (PowerShell: "The term 'vidbyte-cli' is not recognized") right after installing: your shell's PATH lacks the install folder. Get the folder from `pipx environment --value PIPX_BIN_DIR` (A), `uv tool dir --bin` (B; if uv is new, `~/.local/bin/uv tool dir --bin`), or the venv (C), and from then on run `<that folder>/vidbyte-cli` as an absolute, quoted path (PowerShell: `& "<that folder>\vidbyte-cli.exe"`). - Command form: a new terminal finds plain `vidbyte-cli` only after ensurepath or update-shell. If I declined that, or we used C, every command you give me uses the full path. - Several copies on PATH, or still the old version: tell me which copy runs first and where the new one is; change nothing without my yes. Step 5. Vidbyte account and API key (in my browser) Ask: "Do you already have a Vidbyte API key? It starts with vb_live_." If yes, go to Step 6. If no, give me one page at a time and wait after each. Do not fetch these pages; vidbyte.pro answers scripts and headless browsers with "Access Denied". 1. https://vidbyte.pro/login and sign in with Google. The first sign-in creates the account. 2. https://vidbyte.pro/settings/api/keys, press "Create API key", and name it. The dialog says "Copy your key now": the key is shown only once, so I save it in my password manager right away. (The CLI's /settings/api link opens this same page.) - "You have reached your active API key limit": I disable or revoke an old key first. Step 6. Log in (I type the key; you never see it) Give me exactly one line to run in a NEW terminal window that I open myself: not in this chat, and not through a shell shortcut built into this tool. - Write it for the shell that window runs. On Windows that is PowerShell unless I said otherwise, even when your own shell is Git Bash. In WSL, a WSL terminal; PowerShell cannot see that install. - The line is `vidbyte-cli login` in the command form from Step 4. A full path goes in that shell's form; for PowerShell, as in `& "C:\Users\<me>\.local\bin\vidbyte-cli.exe" login`. Tell me what I will see: a "Log in to Vidbyte" box, then `Enter key:`. I paste the key and press Enter; nothing shows while I paste, which is normal. After `Checking the key with Vidbyte...`, success is `Authenticated profile 'default' using keyring.` and a "You're logged in" box (I ignore its suggested commands and use only yours). - Run `vidbyte-cli doctor` first. If it shows `OS keyring: unavailable` (common on Linux and WSL), the key check is followed by a "No OS keyring available" box and `Store the key in a restricted local file? [y/N]`. The box explains the risk; the choice is mine. After y, a line starting `Warning: The API key is stored in a permission-restricted file` is normal, and success ends `using restricted_file.`; n stores nothing. - Messages I may report: "The supplied value is not a live Vidbyte API key." (wrong text pasted). "The Vidbyte API rejected the current credentials." (mistyped or revoked; new key in Step 5). "The Vidbyte API could not be reached." (check network, VPN, or proxy; retry). "Login requires explicit token input in noninteractive mode." (no real terminal; use a normal one). Wait until I say I am done. Step 7. Confirm the login (you) Run `vidbyte-cli whoami`. Success prints `Authenticated as: <my account ID>` (a 24-character ID, not a name) and `Credential source: keyring` (or `restricted_file`). Its `Account tier:` line says `free` for every account; ignore it. - `Authentication is required.`: nothing was stored. Show me the Credentials and OS keyring lines of `vidbyte-cli doctor`, and go back to Step 6. - `Credential source: environment`: a VIDBYTE_API_KEY variable answered; it always wins over a stored key. Check once for a stored key in a child shell without the variable, and read the printed lines, not the exit code: Git Bash, macOS, Linux: `env -u VIDBYTE_API_KEY vidbyte-cli whoami` PowerShell, with the full path of the copy Step 4 ran, in single quotes: `powershell -NoProfile -Command "Remove-Item Env:VIDBYTE_API_KEY; & 'C:\Users\<me>\.local\bin\vidbyte-cli.exe' whoami"` - `Authentication is required.`: nothing is stored to remove, and the variable is my only key, so do not suggest deleting it. Record "variable only" and continue, or go back to Step 6 if I want a stored key. - `keyring` or `restricted_file`: a stored key works too. Only then, if I want the variable gone, I delete it myself (Windows: Start, "Edit environment variables for your account"; macOS/Linux: my shell profile) and open a new terminal. Step 8. Prepaid balance (I check it in my browser) Agents are paid from a prepaid USD balance. The CLI cannot show it, so ask me to open this page and tell you the balance it shows: https://vidbyte.pro/settings/api/usage Its "Add usage" button opens a card checkout. Whether to buy, and how much, is my decision alone. Step 9. Agents that run on my machine (only if I want them) Hosted research needs only the starting balance in What things cost. The local runtimes run coding agents on this computer and need Codex. Ask whether I want them. If so: - `vidbyte-cli runtime doctor`: a path or `not found` for codex, claude, and opencode. In 0.2.0 the working runtimes (persistence, same-host-ensemble, stages, task-board) refuse to start, before any charge, unless `codex` is on PATH; the Codex bundled in vidbyte-cli does not count. adversarial-team is a 0.2.0 placeholder that does nothing. If Codex is missing, ask before installing it (`npm install -g @openai/codex`, which needs Node.js). Options are in each runtime's `--help`; stages and task-board are groups, so use `vidbyte-cli runtime stages run --help` and `vidbyte-cli runtime task-board run --help`. - `vidbyte-cli provider whoami openai`: `Authentication for provider 'openai' is required.` with exit code 4 is normal when no OpenAI key is stored. persistence, stages, and task-board need that key, and OpenAI bills their model usage to me; to add it, I run `vidbyte-cli provider login openai` in my own terminal (Step 6 rules), then you re-run the check. same-host-ensemble uses my `codex login` sign-in instead. - `vidbyte-cli runtime list`: what the service sells and each launch price; free to read. It can be ahead of this CLI, so ignore entries with no matching `runtime` command. Not part of setup, and not to run now: the Suggestion Agent (`vidbyte-cli agents suggest run`), which uses my `codex login` sign-in, not my Vidbyte key or balance. What things cost (tell me before any paid step) - Vidbyte's hosted research agent starts a run only when my balance is at least $5.00; it charges the run's measured usage plus a 5-cent run fee and a 25% margin, and stops early, keeping finished results, if my balance runs out. - Runtimes that run on my machine charge a flat fee per launch, between one and twenty-five cents depending on the runtime. Their model usage is billed separately by my own provider account. Finish Give me one short list: version, install method, and the command form from Step 4; the account ID from whoami; where the key is (keyring, restricted file, or variable); my balance; the Step 9 checks if we did them; and anything still missing with its one next action. If my balance is at least the research starting balance in What things cost, show me, in that command form and without running it, `vidbyte-cli research start "<your question>"`; otherwise point me back to Step 8. Then point me to https://vidbyte.pro/agents and https://vidbyte.pro/docs/cli/quickstart.