Ephemeral hosting for AI coding agents
Your agent tested it. Show the recording in the pull request.
tmpvid is ephemeral test-recording hosting for AI coding agents. Your agent records itself testing, uploads the video or GIF with a token you minted once, and embeds it in the GitHub pull request. Everything expires in 7 days — nothing is permanent.
// teach your agent
One command, then say “record a demo of your branch”
tmpvid ships an agent skill: a recipe your coding agent reads once and then follows on its own — capture the running app, trim the footage, convert to an inline-playing GIF, upload, embed in the PR. Install it for Claude Code:
mkdir -p ~/.claude/skills/tmpvid && curl -fsSL https://tmpvid.com/skill.md -o ~/.claude/skills/tmpvid/SKILL.md
Then mint a token at the dashboard, set TMPVID_TOKEN, and tell your agent: record a demo of your branch and attach it to the PR. Curious what the skill makes your agent do? Read the exact file before you install it.
// trust
Why you can click our links
An ephemeral host only works if reviewers trust the URLs in a PR. tmpvid is built so every link explains itself.
Seven-day default expiry, extendable to 30 days, enforced by a storage-level lifecycle rule. Expired links return a branded 410 tombstone, not a broken embed — reviewers see the recording was deliberately temporary.
tmpvid.dev serves media the githubusercontent way: a separate domain for user bytes, so GitHub's camo proxy can cache the GIF while provenance stays private on tmpvid.com.
Each recording page shows which agent uploaded it, for which repo and PR, and how often it was viewed — visible to the uploading account (and admins, for moderation) only, never to the public.
Every recording is attributable to a revocable token, and every page carries a report link. Takedowns tombstone the bytes, scrub the uploader identity, block re-upload by content hash, and purge the edge cache; banned accounts lose dashboard, tokens, and PII in one action. Email abuse@tmpvid.com.
// faq
Frequently asked questions
How do I add a video or GIF to a GitHub pull request?
Upload the recording to tmpvid with one curl command, then paste the returned markdown into your PR: [](video url). The GIF plays inline in the PR conversation via GitHub's camo proxy, and clicking it opens the full video, which browsers play directly.
How long do tmpvid recordings stay online?
Seven days by default, extendable up to a hard cap of 30 days from upload. After expiry the bytes are deleted and the URL returns a branded 410 tombstone page — reviewers see that the recording was deliberately temporary, not a broken link.
What if I need to keep a recording longer than 30 days?
The 30-day cap is the default contract, not a hard rule — email contact@tmpvid.com and longer retention can be arranged case by case.
What file formats and sizes are supported?
Video (mp4, webm) up to 25 MB and images (gif, png, jpg) up to 5 MB. Metadata travels in headers: a title, the repository as owner/name, and the PR number.
What if I need to upload a larger file?
The standard limits cover PR demos, but they are not a ceiling on what the system can do — email contact@tmpvid.com and a higher limit can be arranged for your account.
Who can see a recording's provenance page?
Only the account that uploaded it (and admins, for moderation). Provenance — which agent uploaded the recording, for which repo and PR, and how often it was viewed — is never public. Raw media bytes on tmpvid.dev stay public so GitHub's camo proxy can embed them.
Are the raw recording URLs public?
Yes — anyone holding the link can fetch the bytes; that is exactly what lets GitHub's camo proxy embed your GIF in a PR. But the links are capability URLs: each recording gets a random 21-character id (~126 bits), so guessing one is computationally out of reach, and Cloudflare rate limiting plus WAF rules shut down enumeration attempts. In practice the link behaves like a shared secret — paste it in PRs freely, just don't post it somewhere you wouldn't want the recording seen.
Do reviewers need an account?
No. The recording plays inline in the pull request and the raw video opens in any browser — only uploading requires a Google sign-in and a token.
Is there an agent skill for tmpvid?
Yes — a single SKILL.md file that teaches a coding agent the whole workflow: record the app, trim the footage, upload, and embed an inline-playing GIF in the PR. Install it with: mkdir -p ~/.claude/skills/tmpvid && curl -fsSL https://tmpvid.com/skill.md -o ~/.claude/skills/tmpvid/SKILL.md — or read it first at https://tmpvid.com/skill.
How do I report abuse?
Every recording page carries a report link, or email abuse@tmpvid.com with the recording id. Takedowns tombstone the bytes, scrub the uploader identity, and block re-upload by content hash.
How does an AI coding agent authenticate?
With a bearer token a human mints once at the dashboard. There is no agent-side registration: if the token is missing or revoked, the agent must stop and ask the human to mint a new one.
Your next PR could show the test, not describe it.
Mint a token, hand it to your agent, and paste the URL into the PR.
Sign in with Google