The Operator carries out the work you ask Playbooks to do. It interprets your request, considers the available context, chooses an approach, uses authorized capabilities, and checks the result. As it learns from the work, it can adjust its next action or ask you for a decision.
The Composer is where you prepare and send messages. The Operator is the repeated cycle of reasoning, action, and review that works on those messages, using configuration, tools, and services within the current resource’s permissions.
Follow the loop
| Stage | What happens |
|---|---|
| Understand | Interpret the outcome, constraints, and relevant evidence |
| Plan | Choose an approach and seek agreement when the task requires it |
| Act | Use available tools and services within current authority |
| Observe | Inspect outputs, failures, and changes in the working state |
| Adjust | Refine the approach, continue useful work, or request missing direction |
| Verify | Check the result against the request and explain what remains incomplete |
The loop can involve several actions before a final response. A tool returning successfully is one observation; completing your request also requires checking the intended outcome.
What supports the Operator
Configuration shapes how work is approached. Tools provide operations the Operator can invoke. Services provide capabilities and resources used during that work. These fit together, but adding guidance or mentioning a resource does not grant access to it.
Work in the right context
Chats, Agents, and Projects provide different contexts for the Operator. Chats use eligible Workspace configuration. Agents are reusable specialists with their own configuration and authorized resources. Projects provide development context for software and its working previews.
The Operator is the intelligence doing the work; an Agent is a durable product resource in which that work can happen. A Site is a separately governed production destination, not permission for the Operator to release changes automatically.
Guide and review the work
Use a message to define the outcome and Sources to supply task inputs. Use Plans when the approach needs review. While work is running, steer or queue a message according to whether it should affect the current task or follow it.
Changes to saved configuration guide future work; they do not silently expand a running Operator's capabilities. Current access restrictions continue to apply. Review the resulting files, application behavior, or external confirmation before treating consequential work as complete.
Example: investigate a change in sales
Ask the Operator to explain a drop in sales using a supplied export. It can inspect the columns, identify missing dates, compare periods, and save a report in the File system. If the evidence does not explain the change, the useful result includes that uncertainty and the information needed next.
You can steer the analysis toward a specific region without restarting the whole request. If the next step requires reading a connected account, that step depends on an authorized Connection, not merely a mention of the service in your prompt.