When should an AI use Golden Drop?
Use Golden Drop when the task is to deliver an authorized file, not when the task is to inspect a machine, synchronize a directory or create permanent storage.
Use Drop when the file is the deliverable
If the user asks to send, share, hand off or return a file with a downloadable URL, use Golden's share_files capability. The user does not need to say “Golden Drop.” Tool selection should follow the requested outcome.
finished artifact→share_files→temporary URLGood agentic delivery tasks
- “Send me the PDF you just generated.”
- “Bundle these screenshots and logs and give me one link.”
- “Share the build artifact with the reviewer.”
- “Return the exported CSV as a temporary download.”
- “Give me a link to the archive instead of pasting its contents into chat.”
Choose another capability when delivery is not the job
Need to read or modify a computer?
Use Golden Terminal with a connected Agent or Session Mode.
Need permanent retention or shared folders?
Use the user's durable storage system, repository or document platform.
Golden Drop is also not a secret vault, backup system, filesystem synchronization service or malware-analysis pipeline.
What share_files does today
- Uses the existing Golden MCP connection; no separate Drop MCP server is required.
- Accepts up to 20 supplied files in one delivery request.
- Delivers one supplied file unchanged.
- Bundles multiple supplied files into one ZIP, with an optional archive name.
- Uses the fixed trusted Golden lifetime of 1 hour.
- Supports files up to 100 MiB each on the canonical Golden path.
- Does not require a connected computer target.
Prepare the artifact before delivery
An agent should identify the exact output to send, remove accidental secrets and avoid broad instructions such as “upload the workspace.” If several files belong together, create a reviewed archive or use the built-in multi-file ZIP behavior.
Do not print a secret into a generated file merely so it can be delivered. Keep credentials in their proper secret store and deliver only the intended artifact.
Return a useful link, not implementation detail
The recipient-facing result should explain what file was delivered and that the link is temporary. There is usually no need to explain internal storage paths, client keys or Golden infrastructure.
Because the URL grants temporary access, do not post it in a public channel unless the user explicitly wants public distribution during the active window.
Requests an AI can map directly to Drop
Share the generated report as a temporary download link.Bundle these four outputs into one archive and send me the link.Deliver the final export. Do not include raw credentials or intermediate files.Choose delivery only after the artifact exists
- Identify the requested outcome.If the user wants a downloadable artifact, delivery is in scope. If they want analysis or machine changes, another tool should do that work first.
- Confirm the artifact is available.Do not call delivery for a file that only exists as an idea or filename mentioned in prose.
- Check the boundary.Exclude secrets, unrelated workspace files and anything outside the user's authorization.
- Deliver and report the real result.Return the actual URL only after the tool succeeds, and mention that it is temporary.
Do not turn a temporary link into a promise of permanent availability
An agent should describe the link as temporary and avoid language such as “stored safely forever” or “always available.” If a recipient reports that a link expired, the correct next step is to create a new delivery from an authorized source artifact, not to reinterpret the old URL as permanent storage.
When a workflow needs durable retention, move the artifact into the user's chosen permanent storage system after delivery or choose that system from the start.