GUIDE · AI-GENERATED FILES

How to share AI-generated files

When the AI has finished the artifact, delivery should be a small final step: name the file, ask Golden to share it, send the temporary URL and keep long-term storage separate.

QUICK ANSWER

How do I share a file created by AI?

Connect Golden to the AI you already use, then ask it to share the finished file. Golden's share_files capability creates a temporary recipient URL. The recipient opens the link and downloads the file without a Golden account.

AI creates report.pdf→“Share this file”→temporary link
WHAT YOU CAN DELIVER

Use Drop for finished artifacts

Typical deliveries include PDFs, generated documents, images, exported spreadsheets or CSVs, code bundles, build outputs, screenshots, logs prepared for review and ordinary archives.

The important distinction is that the file should already be the intended deliverable. Golden Drop is not a workspace browser and does not decide which private files from a machine should be published.

STEP BY STEP

A practical delivery workflow

  1. Finish the artifact.Ask the AI to generate, export or prepare the exact file the recipient needs.
  2. Review the boundary.Make sure the file does not contain passwords, API tokens, private keys or unintended logs/configuration.
  3. Ask the AI to share it.A simple request such as “Share the final PDF with a temporary link” is enough for tool selection.
  4. Send the returned URL.The recipient needs no account. Treat the active URL as private.
MULTIPLE FILES

Deliver several related outputs as one archive

share_files accepts up to 20 supplied files. One file is delivered unchanged; several files are bundled into one ZIP. This is useful for a report plus attachments, a batch of generated images, or a release package containing several approved artifacts.

report.pdfchart.pngsummary.csv→review-package.zip
LIMITS & EXPIRY

The link is intentionally temporary

The canonical Golden delivery path currently supports files up to 100 MiB each and uses a fixed lifetime of 1 hour. Golden Drop is therefore appropriate for handoff, not archival retention.

If the file must remain available later, move the delivered artifact into the recipient's normal permanent storage after download.

WHEN GOLDEN TERMINAL HELPS

Use Terminal first when the file lives on a machine

If the AI must first build a project, read a server log, collect files from a workstation or create an archive from a connected environment, Golden Terminal handles that execution. Once the final artifact exists, Golden Drop handles the delivery.

SAFE SHARING CHECKLIST

Before you send the link

  • Share only the exact reviewed artifact.
  • Remove raw secrets and credentials.
  • Use a private channel for the temporary URL.
  • Tell the recipient the link expires.
  • Use permanent storage instead if the file must remain available.
TROUBLESHOOTING

If the file cannot be delivered

  • Confirm the final artifact exists and is available to the Golden tool call.
  • Check whether any file exceeds the current 100 MiB limit.
  • If several related files are required, deliver them together as one ZIP rather than generating many separate links.
  • If the source lives only on a computer or server, use Golden Terminal to access or create it first.
  • Never work around a failed delivery by pasting raw binary or secret content into the conversation.
FAQ

Sharing AI files

Does the recipient need to sign in?

No. The active URL is sufficient.

Can I choose an arbitrary expiration time?

No. The current Golden path uses the server-selected 1 hour lifetime.

Can I share several files?

Yes. Up to 20 supplied files can be delivered together; multiple files are bundled into one ZIP.

Should I use Drop for secrets?

No. Use a dedicated credential or secret-management mechanism.