Files & Attachments

Attach files to an orb thread when the task starts with more than text or source code. Amp can work with screenshots, videos, audio, PDFs, logs, spreadsheets, datasets, archives, and other files.

Attach a File

Use the attachment button in the message composer, drag files into the composer, or paste a file from the clipboard. Add instructions that explain what the file contains and what result you want.

Watch this screen recording, reproduce the problem in the app, and fix what causes the layout to jump when the menu opens.
Analyze these logs. Group related errors, identify the first failure in each group, and tell me which one is most likely to explain the outage.

The normal upload limit is 100 MB per file. Users with the higher upload limit can upload files up to 512 MB.

How Amp Uses Attachments

Attachments remain private to the thread and are not automatically copied into the repository. Amp can inspect images, PDFs, audio, and video directly. For other file types, Amp downloads the file into the orb when it needs local tools to read or transform it.

Tell Amp when the original file must remain unchanged or when generated output belongs in a particular directory.

Useful Tasks

  • Record a problem in your app and ask Amp to reproduce and fix it.
  • Attach logs or a diagnostic archive for investigation.
  • Turn a presentation or spreadsheet into an interactive web page.
  • Analyze a CSV or other dataset and build a report.
  • Transcribe or summarize audio and video.
  • Generate a new image, video, document, or model from reference material.

Share Generated Files

Files created in the orb stay in its workspace unless Amp attaches or publishes them. Ask for the kind of result you need:

Create a CSV with the cleaned rows and attach it to your final reply.
Publish the finished demo video so I can share it outside this thread.

Only publish a file when it is safe for anyone with the URL to access it. Regular thread attachments remain protected by Amp’s access checks.