Screenshots inside the transcript
An agent can show you a picture. It copies the file into ~/.v-code-shots and
writes a markdown image line pointing at that file through VCode; the image
renders in the reply, and tapping it opens it full size.
Why you would use it
A browser screenshot, a rendered chart, a diagram — anything where describing it costs more than showing it. On a phone this is the only way to see what a Playwright run actually rendered.
How to use it
As the user:
Ask for a screenshot.
The picture appears in the reply.
Tap it to open the viewer (
#shotview).
The phone's back button closes the viewer and leaves you in the thread; so does the close button (
#shotview-close).
As an agent, from inside a thread:
- Write the image into
~/.v-code-shots/<name>.png. - Emit a markdown image line for it in the reply. The exact path is under How
it works, and the
v-code-screenshotsskill carries it.
What you see
The image renders inline, lazily loaded, at the point in the answer where the
markdown line was. The viewer shows it full size with the image's alt text in
the header (#shotview-name) and the picture itself in #shotview-img. An
image written with an empty alt is titled screenshot.
An attached image you sent renders as a chip on your own message; tapping that opens the same viewer, titled with the file's name.
Options and settings
| Option | Default | What it changes |
|---|---|---|
| shots directory | ~/.v-code-shots, then ~/.portal-shots |
where the server reads the files from (config.shotsDir) |
Limits and known gaps
- Only images from
~/.v-code-shotsrender. A markdown image pointing anywhere else stays literal text — an inline<img>to a third party would leak that you are reading the thread. - The filename must start with a letter or digit, contain only letters, digits,
.,_and-, and end in.png,.jpg,.jpeg,.webpor.gif. Anything else is refused withbad shot name; a name that is not on disk getsno such shot. - The pictures are behind the same login as everything else.
- Files are served, never deleted.
~/.v-code-shotsgrows until you clear it.
Related
- read-the-transcript — where the picture lands
- formatted-answers — the rest of the markdown
- attach-photos-and-files — pictures going the other way
- open-an-attachment — the same viewer, opened from a chip
- log-in-with-the-token — the cookie the
<img>load carries