Cloud Agent: generated files need a more reliable way to access/download

General
1

I’ve run into a recurring usability issue when using Cloud Agent for file-generation tasks.

For example, after the Agent finishes creating a file, it may tell me that the output is saved at a path like:

/data/workspace/deliverables/pitch_deck_page_02.html

The problem is that this is a path inside the Cloud Agent environment, so I can’t access it through Finder on my local machine.

That means I have to ask the Agent to provide a download link. However, the generated download link is sometimes invalid or inaccessible. I can ask it to resend the file, but the new link may still not work.

So the workflow becomes:

Agent successfully finishes the task → file exists in Cloud Agent → user still has no reliable way to retrieve it.

This makes file-based workflows on Cloud Agent quite frustrating, especially for tasks that generate HTML, PPT, PDF, documents, images, etc.

Suggestion

Could Anna provide a more standardized artifact/file-delivery mechanism at the Agent level?

For example:

  • Automatically detect files created by the Agent and expose them as downloadable attachments in the conversation.
  • Provide a persistent Files / Outputs / Artifacts area for the current session or Cloud Agent.
  • Convert internal paths such as /data/workspace/... into user-accessible files automatically.
  • Let the Agent reference a real file object instead of manually constructing download links.
  • Ideally, generated files should remain accessible even after the Agent task has finished.

From a user perspective, if the Agent has already created the file successfully, retrieving that file should be a deterministic platform capability rather than something we need to repeatedly ask the LLM to handle.

I think improving this would make Cloud Agent much easier to use for any workflow that produces files.

1280X1280.PNG
1280X1280.PNG1280×1083 147 KB

2

Hi @Pekky! :waving_hand:

Thank you for this wonderfully detailed write-up — you nailed the problem precisely, and your suggestions are genuinely great. :raising_hands:

Good news first: the broken-link bug is fixed as of v1.1.0-beta.131, which is already live! :tada:

What was happening: when the agent uploaded a file for you, it was sharing a short-lived internal URL (only valid for ~30 minutes) instead of a proper download link. And when you asked it to “resend”, it often just repeated the same expired link — which is exactly the frustrating loop you described. :sweat_smile:

What’s changed:

  • :link: File uploads now come with a long-lived download link (valid for 7 days), and the agent is instructed to always share that one with you.
  • :open_file_folder: The agent no longer reports internal-only paths like /data/workspace/... as the final answer for Cloud Agent sessions — if the file isn’t reachable from your machine, it now uploads it and hands you a working download link automatically.

On your suggestions: we love the idea of a deterministic, platform-level artifacts experience (auto-detected outputs, a persistent Files/Outputs area for the session) — that’s very much aligned with where we want to take Cloud Agent, and your post is great input for that direction. :light_bulb:

Thanks again for taking the time to report this so thoughtfully — feedback like yours directly shapes the platform. Happy building! :sparkles: