Session

One continuous run of an agent against a task, from the first message to the point its context ends — the unit that handoffs bridge

A session holds state only in its context window. Two sessions on the same repository share nothing but the files and the commits, which is why the checkout is shared with care and why a worktree per task became the rule.

On the web, the server-side record of one signed-in visit — created at sign-in, identified by a value the browser sends back on each request, and ended by expiry or sign-out

It exists because HTTP is stateless: the server cannot recognize a second request as the same person unless the first handed something back. That something is usually an HttpOnly cookie holding an opaque identifier, with the real session record kept server-side, so that what travels is a reference rather than the data. This site’s sessions are Better Auth rows in the database, re-checked against the membership lists on every sign-in — which is what makes revoking access a list edit rather than a deployment.