Artifacts and export
Anything the model builds that is not prose — a widget, a deck, a document, a diagram — opens in the panel beside your chat. That panel is where you revise it, move between versions, and take it away as a file.
The panel
It opens on its own when a reply produces something worth showing, and it stays with the conversation — reopen the thread tomorrow and the artifact is still there at the version you left it.
Each artifact carries its own controls: copy the source, download the file, and step through versions. What is offered depends on what the thing is — a deck offers PowerPoint, a written document offers PDF (saved from your browser’s print window) and Markdown, a designed report downloads as Word, source code offers a copy button.
“Open in new tab” gives an artifact its own page — useful for a second monitor or a screen share. That page is read-only by architecture: it cannot edit, so a stale tab can never fork your work — it shows the artifact as it stood when the tab loaded, and a reload catches it up. The panel itself can also go fullscreen; Escape steps back down — fullscreen to panel to closed — rather than jumping straight out.
Some code artifacts do more than display — React widgets and Python or SQL listings can run right in the panel; how running works lives with widgets.
Opening automatically
When a reply finishes building something that shows live, the panel opens it on its own — on a desktop-sized window, at most once per reply, never over an artifact you already have open, and if you close it mid-reply that decision is respected.
The switch is “Open finished creations automatically”, in the settings dialog behind Instructions at the top of the chat (on a phone: in the account menu at the bottom of the chat list). It is on by default and applies to this device only — each browser remembers its own choice.
Editing by asking
Revisions happen in the chat, not in the panel. Say what should change and the artifact in front of you is updated — a narrow ask is patched in place rather than rebuilt from nothing, which is both faster and less likely to disturb the parts you liked.
- “Make the second slide less dense.”
- “Add a reset button to the calculator.”
- “Change the heading to something plainer.”
One change at a time reads better
Versions and restoring
Every revision is a version. Step back with the arrow buttons or the slider — the label always says where you are, and versions you wrote by hand are tagged “you”. “Latest” jumps forward again. Nothing you had is lost by trying something.
Restoring is a step forward, not an undo
Getting a file out
Vresk writes real office files, not printouts of a web page:
| Format | What it is for |
|---|---|
| .pptx | PowerPoint. Real slides with real text boxes — open it and keep editing in PowerPoint or Keynote. |
| .docx | Word. A designed report downloads as Word; a designed deck can too, as a document rather than slides. |
| PDF. For sending something that should look the same everywhere. |
Widgets and diagrams are copied or downloaded as their source rather than exported to an office format — they are working things, and a file that cannot run is not the useful version of them. More on widgets.