Files, Attachments, and Outputs
Learn how to give files to Cola, limit file scope, and find generated results.
Cola can use files and attachments to read screenshots, summarize documents, analyze tables, organize material, generate Markdown, images, reports, or code changes. For file work, two things matter most: give a clear scope and ask Cola to state the output location.
Add Attachments
Drag files into the input box, or use the attachment entry near the input. After you send the message, Cola treats those attachments as part of the current task.
Good attachment types include:
- Screenshots, images, and design mocks.
- PDFs, Markdown, plain text, and logs.
- Spreadsheets, documents, and exports.
- A small set of files you want Cola to reference.
When sending attachments, say what Cola should do:
Summarize the key points in this PDF as 5 bullet points.Look at this screenshot, identify the biggest usability issue, and do not inspect other files.Compare the fields in these two spreadsheets and give me a difference list.Attachments vs. Authorized Directories
Attachments are best for a small number of files you provide for one task. Cola continues around those files for that task.
If you want Cola to process a directory, project, or nested folder tree, it may request file access. After you allow access, that directory appears in Settings > Privacy > Authorized Directories, and Cola can read or write files inside it.
If you are unsure, do not authorize a large directory first. Say:
First list which files you need. Do not read the whole directory.For this task, use only the attachments I dragged in. Do not access other local files.For more detail, see Tasks and Permissions.
Ask Cola to Generate a File
If you want a saved result, state the file format and content directly:
Write the result as a Markdown file and tell me the file path.Create a troubleshooting report I can send to a teammate, saved as Markdown.Turn these screenshots into an issue list and output it as a spreadsheet file.If you only say "summarize this" or "analyze this", Cola may reply in chat and not create a file.
Find Outputs
User-visible files generated by Cola usually appear in the Outputs area in the main interface. They may also appear on task cards with preview or Show in Finder actions.
The default output directory is:
~/cola/outputs/If you asked Cola to edit or generate files inside an active project, the result may be in that project directory instead. After the task completes, you can ask:
List every file path generated or changed in this task.Only tell me where the final output file is. Do not repeat the intermediate steps.Preview, Search, and Open
Use Outputs to find files Cola generated. For tasks with many files, search by keyword or open the relevant output folder.
If a file does not appear in Outputs, first confirm that the task actually asked Cola to create a file. You can also ask Cola to check:
Did you generate a file just now? If yes, tell me the path. If not, create a Markdown version now.Confirm Before Sending or Uploading Files
Some tasks send files to external services, such as uploading attachments, calling a model that processes file content, or sending a file to a contact through Cola Link.
For sensitive files, use clearer limits:
First tell me which files you plan to upload and why, then wait for confirmation.Send only the summary. Do not send the original file.Do not paste the full log. Extract only the error type and time.Do not attach passwords, private keys, API keys, recovery codes, identity documents, card photos, or full customer records unless you have confirmed that doing so meets your security needs and organization rules.
Clean Up and Back Up
Output files stay on your Mac. Signing out does not automatically delete them. Before changing computers, reinstalling, or uninstalling, confirm whether you need to back up ~/cola/outputs/ and any project directories Cola worked in.
For more, see Backup, Migration, and Uninstall.