Open a lane
Opens a parallel track inside the session. kind side opens a side conversation that runs without pausing or contaminating the main work; kind subagent delegates to the named agent recipe, running concurrently with other delegated work. The initial message starts the lane’s first turn; its results stream over the event stream. A session holds at most one OPEN side conversation. A side conversation is a conversation, so a follow-up question belongs in the lane that already has one rather than in a new lane that never saw the exchange: list the session’s lanes, find the side lane whose status is not closed, and submit the question to it (createLaneMessage). Asking for a second one answers 409 and names the lane that holds it. Closing the open one and opening another is how a fresh side conversation is started.
Path Parameters
The session's id.
Body
Request to open a lane. kind side opens a side conversation; kind subagent delegates to a named agent recipe — agent is required in that case, and ignored for kind side.
side, subagent The initial message that starts the lane's first turn.
1The agent recipe to delegate to. Required when kind is subagent. Ignored when kind is side: a side conversation always runs the host's read-only explorer, and the lane comes back naming it — an unknown name here is neither honoured nor refused.
128Response
The opened lane.
A parallel track of execution inside a session. The main lane carries the primary conversation; subagent lanes carry delegated work; side lanes carry conversations opened mid-run without interrupting the work. Workflow lanes carry one step of a workflow run: they have no parent lane and sit at depth 0, because a run starts from a request rather than from anybody's turn.
main, side, subagent, workflow idle, running, waiting, closed The agent recipe running in the lane, for subagent and workflow lanes.
What the lane is currently doing, in one line.
1024
