Working with Results
This page follows your material through the app: what you put in, what you take out, and the shortcuts that make both faster.
Attaching files
You can upload files and use them as context in chats.
Supported formats
- Images: PNG, JPG, GIF, WebP
- Documents: PDF (text extraction)
- Text: MD, TXT, CSV, JSON, code files
- Office: DOCX, XLSX (text and table extraction)
Limits
- Max 10 MB per file
- Max 5 files per message (files and research documents combined)
- Of these, at most 3 research documents per message
Upload via the paperclip in the composer or Cmd+U. Attachments show as a preview: thumbnails for images, badges for documents.
How a file becomes context
On upload, the content of each file is extracted server-side: text and code are read directly, while text and tables are pulled out of PDF, DOCX, and XLSX. When you attach a file to a message, that extracted text flows into the chat response as context.
Images are the exception. They are not extracted as text but passed to a vision-capable model as an image (see Vision).
Two routes lead to the same place:
- Project files are assigned to a project, appear in the sidebar, and can be attached again and again in that project's chats.
- Directly attached files are added to a single message as you write it.
In both cases, a file only becomes context once it is attached to the message in question. Files and research documents can be attached together (see Research): files provide raw material, research documents provide already-prepared, reusable knowledge from earlier runs.
Attached file context applies to chat responses. Agents and research do not use it directly; their results are stored as research documents that you can later attach in a chat.
What matters: attach the relevant files specifically, not entire archives. Very long extracted text is truncated; a few focused files give better context than a large, unspecific pile.
Saving responses as a file
Responses can be saved as a file (artifacts). Artifacts are only created by a deliberate action; there is no automatic generation.
Available formats: Markdown (.md), CSV (.csv), Excel (.xlsx), PDF (.pdf), and Word (.docx).
- Below an assistant or agent response, choose Save as file.
- Select the desired format.
- The artifact is generated and stored server-side.
For CSV and Excel, tables from the response (Markdown tables) are carried over; otherwise the text is stored line by line.
After creation, an artifact chip with a download appears below the response. The sidebar has an Artifacts section, per project or under "Recent". Deleting removes the file and the entry.
Creating artifacts requires an active subscription.
Keyboard shortcuts
Keyboard shortcuts are a web feature. On macOS use Cmd, on Windows and Linux use Ctrl.
| Action | Mac | Windows |
|---|---|---|
| New chat | Cmd+K | Ctrl+K |
| Send message | Cmd+Enter or Enter | Ctrl+Enter or Enter |
| New line | Shift+Enter | Shift+Enter |
| Toggle Voice | Cmd+Shift+V | Ctrl+Shift+V |
| Upload file | Cmd+U | Ctrl+U |
| Open settings | Cmd+, | Ctrl+, |
| Push-to-talk (recording) | hold Shift | hold Shift |
| Close modal/dialog | Escape | Escape |
You can also find an overview in the settings under "Keyboard Shortcuts".
Security
The same rules cover uploaded files and generated artifacts:
- Uploaded files are validated via MIME type and magic bytes, which protects against misdeclared files.
- Storage is in private object storage; delivery runs through short-lived, signed URLs.
- The content of an artifact is loaded server-side from your own message or your own run. The client does not send any file content.
- Access is restricted to your own account (Row-Level Security).