Lanes, zoomed in

Lanes could already lay a week of agent work out over time. It can now be interrogated. ⌘ + scroll zooms the track and dragging pans it, so the same view goes from a week at a glance down to what happened inside a single hour, without changing filters or leaving the page.

Hovering a session splits its elapsed time into run and wait — wait being the gaps between spans, the idle that agent hours deliberately exclude. That is the difference between a session that took four hours and one that worked for four hours, and until now it was invisible.

Clicking an engineer's avatar opens a sheet for that person over the current window: occupancy, average and peak concurrency, sessions, turns, agent hours, tokens, and cache read rate. If you are trying to work out how your team actually uses agents — where the waiting goes, who runs work in parallel — that is the question Lanes now answers.

The figures stay honest about their own limits. When the window holds more sessions than the pool can draw, or turns and tokens cover only part of it, the footer says so instead of quietly showing you a smaller number.