Agent Workspace
How to use the main working surface for prompts, follow-ups, and long-running tasks.
Agent is where work starts and where most people spend the largest share of their time. The page is built around a single thread of work. You ask for something, watch the task unfold, then either refine the result in place or turn the finished approach into something more repeatable elsewhere in the product.
How to think about a session
A session is not just a one-message exchange. It is the running thread that holds the history of what you asked for, what changed, and what the next instruction should build on. That matters because the strongest results usually come from staying in the same thread long enough to refine the first pass instead of restarting from scratch.
What makes a strong prompt here
A strong prompt gives the page something concrete to aim at. Name the outcome, the intended audience, the tone, and anything the result must avoid. When the first answer is close but not quite right, change the direction clearly instead of adding vague pressure. Agent responds better to specific steering than to repeated “make it better” follow-ups.
What the page is good at
Agent is strongest when the outcome needs judgment, iteration, or coordination. Drafting, summarizing, reviewing, researching, rewriting, and preparing handoff material all fit naturally here. If the same request keeps coming back in slightly different forms, that is usually the signal to move the pattern into Macros, Automations, or Workflows.
What to watch while a task is running
The current task state tells you whether the work is still in progress, completed cleanly, or needs attention. When a task is already moving in the right direction, stay in the same thread and sharpen the brief. When it is clearly drifting, reset the instruction instead of layering on more vague follow-ups.
What belongs elsewhere
Agent is not meant to be the place where recurring infrastructure lives forever. Once a pattern stops being exploratory and starts becoming routine, move it into the part of the platform built for repeatable work. That shift keeps the chat area focused and makes the system easier to manage later. A reusable specialist usually belongs in Assistants. A repeatable task belongs in Automations or Workflows.