Guides
Attachments
Give the agent screenshots, configs and logs.
Attach files to a message when words are not enough: a screenshot of the problem, a config file from your server, a stack trace from the console.
How to attach#
Use the paperclip button in the thread composer and choose files. Each file appears as a chip above the message. Remove a chip to leave that file out of the message.
What is accepted#
| Kind | Types | Size |
|---|---|---|
| Images | PNG, JPEG, WebP | up to 8 MiB each |
| Text files | .txt, .md, .java, .yml, .yaml, .json, .xml, .properties, .log, .csv, .gradle, .kts | up to 128 KiB each, valid UTF-8 |
You can attach up to 5 files to one message. Each project can hold up to 100 attachments and 256 MiB in total.
Archives, executables, PDFs, SVG and HTML files are not accepted. File contents are checked, not only the extension.
When to use which#
- Console log or stack trace: attach the
.logor paste the relevant lines. Tell the agent what you were doing when it happened. - Config files: attach your real
config.ymlso changes match the format you use. - Screenshot: useful for GUI layouts or an error shown in game.
The agent can only read an image if the model you picked supports images. If it ignores a screenshot, switch to a model with image support or describe the image in text.
Privacy#
Attachments are stored privately with the project, not in a public location. Removing a chip from a message does not delete the upload from the project, and attachments are sent to the model provider you chose along with that message. See Security and privacy.
Limits#
Uploading is rate limited to protect the service, so very rapid repeated uploads can be refused for a moment. Wait a little and try again.