Files and attachments
Attach files and images to a chat so your agent can read them. Works in the iOS app and the web app. Pick them from the composer, send them with your message, and just say "look at this." The agent gets the paths under the hood and reads them straight off your own machine.
What it is
An attachment is a file or image you hand to the agent inside a chat session. A screenshot of a stack trace, a log dump, a CSV, a design mockup, whatever you want the agent to look at. You add it from the composer, it rides along with your next message, and the agent can read it back while it works. The flow is the same on the iOS app and the web app.
Up to 100 MB each
Each file can be up to 100 MB. Attach several at once and they queue in a tray above the composer, so you can stack a few up and send them together with one message.
Where they go
Uploads land in a folder on your own daemon host, not in the cloud. The default is ~/.codeout/uploads. The daemon owner can change that folder in Settings, and the daemon hard-validates the path so it always stays inside your home directory. Files never leave your machine, and they travel between your device and your daemon over the same end-to-end-encrypted channel as everything else in codeout.
Using it
Tap the attach button in the composer to pick files or images. When you send the message, the file names and paths are handed to the agent under the hood, so you can just write "look at this" or "what is wrong in this log" and it reads them. Because the files live in your own upload folder and you put them there yourself, reading an attached file is auto-allowed: no permission prompt, no Allow tap.
Viewing files
Images preview inline in the chat and open full-size, with a download button. Other file types are download-only: codeout serves them as attachments, so they are saved to your device rather than executed or rendered in place. Tap any file to pull it back down to whatever device you are on.
Good to know
Attachments follow the same rule as the rest of codeout: your data stays on your hardware. There is no third-party upload server in the middle, and the transfer is encrypted end to end. For the full picture, see Security and encryption and Privacy.