> A worker reads the tail of the log, performs exactly one step—either inference or tool execution—appends the result, and forgets everything. It holds zero session state between turns.
My current understanding of an agent session is that the entire session (modulo compaction, reordering tools, etc) is sent to the stateless inference engine every time inference happens. The quoted section doesn't seem workable unless "read the tail of the log" actually means "read the entire session log".
There are ways to make that work but workers being completely stateless makes it hard.
First, the worker has to read the entire session log only if the next action is inference.
You are right that my writing is misleading. To clarify that, I mean the worker only needs the tail of the log to decide what to do next: inference or execute tools.
> A worker reads the tail of the log, performs exactly one step—either inference or tool execution—appends the result, and forgets everything. It holds zero session state between turns.
My current understanding of an agent session is that the entire session (modulo compaction, reordering tools, etc) is sent to the stateless inference engine every time inference happens. The quoted section doesn't seem workable unless "read the tail of the log" actually means "read the entire session log".
There are ways to make that work but workers being completely stateless makes it hard.
First, the worker has to read the entire session log only if the next action is inference.
You are right that my writing is misleading. To clarify that, I mean the worker only needs the tail of the log to decide what to do next: inference or execute tools.