Skip to main content
A session holds the execution and conversation context for agent work. The colony is the longer-lived workspace; sessions and workers represent the activity within it. For most tasks, use the colony’s chat rather than managing session identifiers. Send corrections in the same colony so they reach the intended work.

​
When an agent asks a question

Read the question and answer in that colony. Give the missing decision or information clearly. If the task needs to stop before sending or changing something, state that requirement in the initial brief. The ability to ask for input does not mean every workflow automatically stops before every external action. Templates and skills can contain instructions to execute actions directly.

​
Follow delegated work

Open Automation → Workers to inspect the agents handling parts of the task. A worker can still be active while the queen is quiet. Inspect the worker’s details or transcript when a result is missing or unexpected.

​
Continue after a stop or error

Use the status tooltip to distinguish a normal turn ending from a retryable error. Correct the cause if you can, then send a specific follow-up. Before retrying an external write or send, inspect the destination to see whether it already happened. Repeating the instruction without checking can duplicate work. For recurring invocations, see Scheduling. For the current UI controls, see Working in a colony.