Output destination

An output destination is the specific place an agent writes its result, such as a named folder, a draft email, or a note. You pick a spot you already check so the output lands inside your normal review window.

An output destination is the specific place an agent writes its result, such as a named folder, a draft email, or a note. When you set up a recurring agent, you tell it both what to produce and where to leave the finished work. Say you schedule a morning agent that drafts a summary of your unread messages. If you route that summary into a folder you open every day, you read it as part of your routine. If you route it into a new app you rarely open, the agent keeps running and producing summaries no one ever sees. The destination decides whether the work reaches you or quietly piles up unread.

Builder example

An agent that produces good output into a place you never look is the same as an agent that produced nothing. A daily research agent might write a sharp brief into a brand-new dashboard, and three weeks later you discover a stack of briefs you never opened. Tell the agent to write into a destination already in your routine, such as a draft in your inbox or a file in the folder you check each morning, so the output meets you instead of waiting for you to remember it.

Common confusion: Choosing a destination is not the same as choosing a tidy place to store output. The test is whether you will see the result during your normal review, not whether the folder looks organized. A perfectly filed report you never reopen still wastes the run.