Ejecting

e on a running row in the Work panel stops that agent, frees the lane, and hands back the runner’s own resume command — so the headless run becomes your interactive session, in the workspace lerp leaves standing.

What ejecting does not do

Nothing is written to Linear. The ticket keeps its claim and its status, because ejecting is taking the work over rather than abandoning it — and a claim that stayed put is what keeps the next pass from starting the stage again underneath you.

Nothing is disposed either, so the workspace, its git worktree included, is now yours to finish in and yours to remove.

The resume command

The command is shown until you dismiss it, and it also lands in .lerp/loop.log, so it survives the dismissal and the session.

It comes from the runner’s resume line in lerp.toml , built from the session ID lerp generated before the run started and the workspace it provisioned. A runner with no resume in its config cannot be ejected, so e is not offered on its runs at all rather than failing when pressed.

When to reach for it

Ejecting is the operator’s call and nothing else’s. A run’s activity line and sparkline say whether an agent is still working (see watching a run ), but lerp sets no threshold on them and never acts on one: there is no timeout that ejects a stalled run for you.