How do you get an agent to publish on a schedule with no human in the loop?

A nightly job runs, an agent generates a report, and normally that means someone has to notice the job finished, find the output, and send it somewhere. If the job runs at 3am, nobody is watching, and the report sits in a container that will be gone by morning.

The publish call is a single HTTP request, or one CLI command, so the last step of the pipeline can call it directly. Nobody has to click "share." Tag the call with the session and agent that produced it, and the page carries that context from the moment it goes live.

Because the artifact is pushed and published in the same step, there's nothing left to clean up once the run finishes. If the pipeline hands work between multiple agents before this last step, see multi-agent file handoff; if it runs somewhere ephemeral, like Lambda or a recycled container, see storage for ephemeral compute.