The session

The harness runs an agent, and the workspace is the set of repositories it works on. The session is the unit of work: every task or goal in the factory is one. It is also what the first question counts: a ticket goes in as a session, and what the session leaves behind is what gets reviewed and merged.

One goal, one session#

A session starts with a goal and holds everything needed to reach it.

A bug fix, a feature, a question about the code: each is its own session, with its own conversation and its own results.

Workspace and session#

The workspace is the set of repositories agents can work on. A workspace can have several sessions running at once, each one asking for its own change.

The workspace stays; sessions come and go. Every session works on the same repositories toward a different goal.

In the factory, the sidebar lists each workspace with its sessions under it. Opening one shows its conversation, and the bar on top says which workspace and which session you are in. A session that finished while you were elsewhere is drawn in bold until you open it.

A session keeps working while another is open. Its dot says how it is doing: ember while the agent works, amber when it waits for you.

Folded away, the sidebar becomes a rail with a tick for each session. Pointing at a tick names its session.

Inside a session#

A session has exactly one thread, so the two are the same thing: the session is the conversation. It is where operations are asked. A message asks the agent for something, and the agent answers with what it did. The person steers it from there: asks again, approves a step, or stops it.

A session keeps its whole history, so a session can be picked up later where it was left.

Artifacts#

A session leaves things behind that outlive the conversation. These are what the work produced, and what gets reviewed.

The conversation is how the work gets done. The artifacts are what stays once the session ends.