lerp Docs Why v0.1.0

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. The headless run becomes your interactive session, in the workspace lerp leaves standing. Lerp never ejects anything on its own, so a stalled run waits for you.

e the resume command esc

What stays

Nothing is written to Linear. The ticket keeps its claim and its status, so the next pass will not start the stage again underneath you. Nothing is disposed either. The workspace, git worktree included, is yours to finish in and yours to remove.

The resume command

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

It comes from the runner’s resume line in Configuration, built from the session ID lerp generated before the run started and the workspace it provisioned. A runner with no resume cannot be ejected, so e is not offered on its runs.