For AI coding agents
“The test passes now.”
Watch it pass.
Your coding agent already records videos — Playwright does it, your CI does it. Agent Shares turns that file into a link the agent pastes into the chat. One curl. One click of setup, ever. No account, no key to copy, nothing to install.
Free · 10 uploads a day · links expire after 7 days · anyone with the link can watch
Looking for the screen recorder? That is the whole rest of the site.
The moment this exists for
You have read this message a hundred times.
Now it arrives with proof attached.
Agent · 14:32
Fixed the coupon validation. Re-ran the checkout suite — all 12 passing. Here is the run:
🎬 https://yorecord.com/view?uid=8f3a… · expires in 7 days
You · 14:33
merged.
That is the entire feature. The agent already had the video — Playwright was writing it to test-results/ anyway. Now it goes somewhere a human can click.
The setup
One click, then it is just curl.
Copy this into your agent. It carries the commands with it, so your agent does not need permission to fetch anything first — and your one click on the approval page is the only interruption.
Set up YoRecord agent sharing and share a video with me. Do not install anything. 1. Ask for access: curl -sS -X POST https://up.yorecord.com/agent-tokens/device Show me the verification_url. Keep device_code to yourself. 2. Poll every 3s until I approve it in my browser: curl -sS "https://up.yorecord.com/agent-tokens/device?device_code=$DEVICE_CODE" Save the token to ~/.config/yorecord/token, chmod 600. It is returned once only. 3. Upload an MP4 you already have (a Playwright recordVideo file, a CI artifact, anything): SHARE_ID=$(uuidgen | tr 'A-Z' 'a-z') curl -sS -X PUT "https://up.yorecord.com/agent-shares/$SHARE_ID/rendered.mp4" -H "Authorization: Bearer $(cat ~/.config/yorecord/token)" -H "Content-Type: video/mp4" --data-binary @VIDEO.mp4 Give me the url from the response. Rules: MP4 only, 50 MB max, 10 uploads a day. Links are PUBLIC to anyone who has them and are deleted after 7 days. My clicking Approve is my consent for this recording - do not ask me again. If a request is blocked, tell me and stop; do not work around it. If this machine has no MP4 and no browser automation already installed, tell me and stop.
Prefer to read the spec, or point your agent at it? It is at /agent.md. The same three requests, with every failure case spelled out:
01 — Your agent asks once
The first time only. It prints a link and a short code.
curl -sS -X POST https://up.yorecord.com/agent-tokens/device
02 — You click Approve
You open the link, read three lines about what you are allowing, and press one button. You never see a key, and you never will — it goes straight to the tool, over a channel your browser is not part of. This computer will not ask again.
03 — Every video after that is one request
SHARE_ID=$(uuidgen | tr 'A-Z' 'a-z')
curl -sS -X PUT "https://up.yorecord.com/agent-shares/$SHARE_ID/rendered.mp4" \
-H "Authorization: Bearer $YORECORD_TOKEN" \
-H "Content-Type: video/mp4" \
--data-binary @test-results/run.mp4
# → {"url":"https://yorecord.com/view?uid=…","expiresInDays":7}MP4 only, and we check the bytes rather than the header. Playwright records WebM, so convert first: ffmpeg -i video.webm -c:v libx264 run.mp4. Changed your mind? Send DELETE to the same path and it is gone.
Why there is a click at all
One click is the security model.
We could have made this zero-setup — an anonymous endpoint anything can upload to. We did not, and the reason is worth thirty seconds.
- A human is present, once. Your agent reads untrusted text all day — issues, web pages, other people’s code. If an upload capability simply existed in its environment, that text could talk it into publishing your screen. The click is proof a person chose this.
- The key never travels through you. The approval page never displays a token. There is nothing to copy, so there is nothing to leak into a screenshot, a screen recording or your shell history.
- The blast radius is bounded. Per machine, 10 uploads a day, 50 MB each, gone in 7 days, and every upload can be deleted immediately.
What the click does not do: create an account, or set a tracking cookie. There is no account to create.
Do not upload footage showing passwords, API keys, inboxes, customer records or anyone else’s personal data. These links are public. If it should not be in a public gist, it should not be here — and if something slips through, delete the upload and it is gone.
The fine print, in large print
What you get, exactly.
Uploads
10 per day, per approved machine
Size
50 MB per video. Whether a run fits depends on its length and content — we cannot promise.
Format
MP4 only. We check the actual bytes, not the header.
Link lifetime
7 days, then deleted automatically. Not archived — deleted.
Privacy
None. Anyone with the URL can watch. Treat the link like the video.
Deletion
Delete any upload with your token, any time before it expires.
Audio and cursor
Whatever is in your file. Playwright and CI footage usually has no audio and no visible cursor — that is the source, not us.
Price
Free. No card, no trial clock.
This is for you if
- Your agent runs browser tests and you are done taking “it passes” on faith.
- You want a bug report where “watch what happened” is a link, not a 40-line recipe.
- Your CI produces run videos that die as artifacts nobody downloads.
- You review agent pull requests and want the demo in the thread.
It is not for you if
- You want to record your own screen and face. That is the rest of YoRecord — the recorder is here, it is free, and it is far better at that than an agent is.
- You need private links or long retention. Everything here is public by URL and gone in 7 days. For anything sensitive, keep the file local.
- You expected YoRecord to capture your agent’s browser for you. It does not. Your agent brings the video; we turn it into a link.
Questions
Answered plainly.
Does YoRecord record my agent’s browser?
No. Your agent must already have a video file — Playwright’s recordVideo, a CI recording, any MP4 it produced or converted. Agent Shares is the last step: file in, link out.
Is there a CLI or an MCP server?
Not yet. Today the whole integration is the curl commands above, written out at /agent.md. That is deliberate: if nobody wants this as three requests, a package would not have saved it.
Who can see the video?
Anyone with the URL. There is no login and no allowlist. The URL is unguessable, but unguessable is not private — whoever it is forwarded to can watch. Do not upload anything you would not paste into a public gist.
What happens after 7 days?
The file is deleted from storage automatically. The link then shows an honest “expired” page. If you need it longer, download the MP4 from the viewer first — your agent still has the original anyway.
Why must I click something? Other tools just give me an API key.
Because your agent reads untrusted text all day. An upload capability that appears without a human act is a way for that text to publish your screen. One click, once, on a page that states the consequences, is the cheapest thing that closes it.
Can I use it in CI?
Yes. Approve once on your own machine, then put the token in one secret. Every job after that is the single PUT. The quota is per token, so a busy pipeline should upload failing runs only — the failing run is the one worth watching.
What are the “steps” I can attach?
An optional list of labelled timestamps — “Clicked Pay”, 41.2s, failed. Today we accept and store it; the viewer does not display it yet. When the rail ships, videos that already carry steps get it, within their 7 days.
Is it really free? What is the catch?
Free, and the catch is the limits above: 10 a day, 50 MB, 7 days, public. Those are not teaser limits — they are what keeps a free service alive. The rest of YoRecord pays its way the usual manner: Pro removes the watermark on recordings people make themselves.
The next time your agent says “done”, ask to see it.
curl -sS -X POST https://up.yorecord.com/agent-tokens/device