The task is the durable thing
People close tabs, move between interfaces, and come back tomorrow. Useful work should have a record that survives those interactions: an objective, an owner, acceptance criteria, current status, and a result. That is a Task. A chat can create or inspect one, but the chat does not need to be its whole existence.
A session is an execution
A Session is a single execution of an agent working on the task. An investigation might need an initial session, a retry after a provider failure, and another session to address the reviewer’s questions. Those executions belong to the same task, while retaining their own boundaries and authorization context.
Reconnection is not unrestricted access
Continuing work requires current authority. An expired grant should not become valid because someone reopens an old session. Sharing a report should not automatically share the credentials or permissions used to create it. Reading, continuing, and forking deserve separate decisions.
One model of work, several interfaces
A person might configure a workspace with Terraform, assign a task through the UI, inspect its progress through the CLI, and review evidence in a developer tool. Using the same Agent and Task concepts across those interfaces reduces duplicate systems and gives teams a common way to understand the work. That is the direction behind Entergenie’s platform design.