Lanes
Agents often work side by side, each in its own worktree. Up to 5 checkouts can record at once, across all workspace folders. Each is a lane: its changes queue on their own, with their own playback position, a color and a name (the branch, or the short commit when detached). One lane is followed: only its changes are typed, in the replay editor, with the usual controls. The others keep recording and wait.
- Checkouts (in the Agent Typewriter Activity Bar view) lists each folder’s checkout and every other worktree git lists. Tick a box to record that checkout in its own lane, clear it to stop. Choose Checkout… is the same choice as a multi-select list.
- Each row and lane node shows its queue. The followed checkout’s row has an eye in its lane color, a tinted name with a ▶ badge, and says whether it is typing, caught up or how many changes wait; the view’s header names it. Click the eye on another lane, or run Follow Lane…, to follow it. Following picks up where that lane was left and keeps playback paused or playing as it was. The status bar entry names the followed checkout and how many record.
- Auto-follow (the eye in the Checkouts title bar, or
autoFollow): once the followed lane is caught up and nothing has been typed for 3 seconds, playback follows the lane whose oldest queued change came first. It never switches in the middle of a change. - Auto-record (
autoRecordWorktrees): a worktree added while recording is watched at once but gets its own lane only when something is written there. Until then it is not ticked in Checkouts, doesn’t count toward the 5 or makerotatestop a lane, and can’t be followed, so the throwaway worktrees review tools check out, read and remove leave no lanes. At its first change,fillgives it a lane while fewer than 5 record;rotatealso makes room by stopping the lane idle longest, never the followed one or one that changed in the last 2 minutes. When neither has room, that change and the worktree are not recorded, and the output channel says why. At most 5 new worktrees wait for a first change at once. Tick a waiting worktree to record it right away. New worktrees outside the workspace folder are noticed too; worktrees that were there when recording started, or before a reload, are not new. - Ignoring throwaway worktrees (
autoIgnoreWorktrees): review tools and scripts often make short-lived worktrees and write a diff into them. List glob patterns for those, and auto-record never gives them a lane and auto-follow never moves to them. A pattern without a slash matches the worktree’s directory name (review-*). One with a slash matches its full path as git reports it, with symlinks resolved (on macOS/tmpis/private/tmp), so start it with**/(**/T/tmp.*).branch:review/*matches the branch instead, and a detached worktree has none. A lane auto-record added since recording started stops, keeping its changes, once it matches, unless it is its folder’s last; a new worktree still waiting for its first change is no longer watched. Your folder’s own checkout never matches, and you can still tick a matching worktree to record it; auto-follow won’t move to it, though a stopped lane that plays out still hands playback to the next lane with changes. Right-click a row in Checkouts and choose Don’t Auto-Record Worktrees Like This to add a pattern, suggested from the row’s name (review-mr-203suggestsreview-mr-*). - A lane that stops recording, because you cleared its box, rotation stopped it, or its worktree was removed, keeps its changes and can still be followed. Lanes the Checkouts view no longer lists show under Not recording.
- While more than one lane is in the buffer, replay tabs are tinted in their lane’s color with a two-letter badge, and the replay editor’s status row starts with the lane’s name. With one lane, everything looks as before. Lane colors are the theme colors
agentTypewriter.lane1toagentTypewriter.lane5. - Two agents in the same checkout still share one lane: the file watcher cannot tell them apart.
- Multi-root workspaces: each workspace folder records in its own lane, so only the followed folder replays. Earlier versions replayed every folder’s changes on one timeline. To replay them all again without picking, turn on
autoFollow: playback then moves to the next folder with queued changes whenever the followed one goes quiet.