Skip to main content
A session is one run of work inside a colony. The colony is the durable thing — its goal, its queen, its history. Sessions are the individual passes of execution against that goal. This split is what lets colonies do long-running work. A colony that runs an outbound program isn’t a single conversation that eventually hits a limit; it’s a standing team that starts a fresh session each time there’s work to do, carrying forward what it learned.

​
Live status

Sessions report status while they run, so both the colony view and the Org Chart show you what’s happening right now without opening anything.

​
Human-in-the-loop

Sessions pause rather than guess. When an agent hits a decision that needs you — a list to approve, a campaign to confirm, a judgment call about a prospect — it stops and asks in the colony chat, then resumes from where it left off once you answer.
A message you type while a session is starting up is queued and delivered to that session. Switching to a different colony or queen clears the queue, so a message meant for one colony is never delivered into another.