Dana runs a one-person design studio. On Thursday she has a call with her client, Northwind Cafe, to go through October: how visits, orders and revenue moved week by week after the new menu page went live.
She asks her agent for a report. A few minutes later the agent replies: done, it's an HTML page with three numbers, a bar chart you can switch, and a table.
When an agent hands something back, writing comes as Markdown. Anything with layout, charts or buttons comes as HTML. This report is the second kind.
We made a 64-second video of this: watch it on YouTube. This post is the written version. The screenshots are frames from the video; Dana, her studio, the cafe and the numbers in the report are demo data.
Three rounds of searching before you see it
The report is done, but Dana hasn't seen it yet.
First she asks where the file is. The agent gives her a path. She opens a folder, clicks down one level after another, finds the file and double-clicks it. A new browser tab opens, and there is the report.
She reads it once and asks the agent to shorten a heading. Done. Then the same questions come back. Is it still the same file, or is there a new one now, and in which folder?
Near the end of the day she wants to go over it once more on her phone before the call. The file is on her laptop, so it has to get to the phone first: a cable, a cloud drive, or emailing it to herself. Then she needs something on the phone that will open it.
Making the report took a few minutes. The time went into finding it, opening it, and moving it to another device.
In udctl, the report is on the card
Here is the same thing in udctl (UnDercontrol).
Dana has a card, "Northwind Cafe: October report", listing the steps: pull the October numbers, build the report page, walk the client through it on Thursday's call. When the agent finishes the report, it attaches it to this card.
She opens the card and the report renders right there, under the to-do list. No asking where it is, no digging through folders.
The file is also in the card's attachments. Click it and a preview window opens: the page on the left, file details on the right.
When the agent changes something, the file is still on the same card, so there is nothing to find again. Refresh the card and you see the new version.
The page in the card works
What shows in the card is the web page the agent built. Scripts run and buttons work.
Dana clicks Revenue and the bar chart switches to revenue. She clicks the last bar and the amount for that week shows below it: October 22 to 31, $8,440.
For more room, open the file page and click Full Screen. The report fills the window.
On the phone, nothing to transfer
On the way home, Dana opens the same card on her iPhone and taps the report in the attachments. The page opens inside the app. She taps the button in the top-right corner for full screen and scrolls down to the chart.
The file was on the card all along. Laptop and phone show the same file, with no transfer step in between.
A page your agent wrote is safe to open
The report has scripts in it, and Dana hasn't read every line the agent wrote. She doesn't have to. The page runs in an isolated frame and can't reach her udctl account.
How to get your agent to deliver this way
Claude Code, Codex, OpenCode, or any terminal-based agent can deliver this way once the ud CLI is installed. Tell it:
Make the report a single-file HTML, attach it to this card, and add a link line in the card body so it shows right there.
The agent attaches the file to the card with ud upload resource, then writes a line in the card body that links to it. You can also upload the file yourself from the card's attachments in the web app.
Two things to know. Only single HTML files work for now: styles, scripts and images have to be inside the file or loaded from a CDN, and a separate CSS file or image in the same folder won't load. On the iPhone, open the file from the attachments; the link line in the card body shows as plain text there.








Top comments (0)