Attachments
Files ride along with a prompt. Anything you attach is queued as a chip under the composer and sent with the next message; nothing is uploaded until you press Send, and clearing the composer clears the queue.
Three ways to attach
| How | What it takes |
|---|---|
Paste (Ctrl/⌘ V) | An image on the clipboard — a screenshot, a copied picture |
| Drag and drop | Any files, dropped anywhere on the composer |
| 📎 | Any files, through your platform's file picker |
Pasting text works as it always did. The app checks the clipboard for an image first and only falls back to the text paste when there is none, so you never have to think about which kind of paste you are doing.
A pasted image has no name of its own, so it is written to a temporary file called paste-<timestamp>.png and attached from there.
The chips
Each queued file gets a chip with its name and size. Images show a thumbnail; everything else shows a paperclip. The × removes one.
Attaching the same file twice — picked once, dropped again — leaves one chip. Hovering a chip shows the full path, which is how you tell two files with the same name apart.
The 20MB limit
A single file over 20MB is refused, with a line under the tray naming it. The limit is the core's, not the app's: the daemon rejects an over-sized attachment outright, and catching it in the composer is better than finding out after a turn has already failed.
There is no limit on how many files you attach, only on how big each one is.
What the agent receives
The daemon runs on your machine, so the app sends paths, not copies. The agent sees the file where it actually lives, and a 20MB image never travels through the app at all.
Sent files appear inside your own message in the transcript — images inline, other files as 📎 name — so the thread is a record of what the agent was given, not just what you typed.
A file with no text is a valid prompt. Attach a screenshot, press Send, and the agent gets the image on its own.
After a reload
Attachments belong to the message you sent, and the core does not echo your prompt back. Reopening a thread replays the agent's side of the conversation, so previously sent attachments are not redrawn. The files themselves are untouched — nothing here ever copies, moves or deletes anything.