Overview

Lerp is one binary and one screen. You put tickets on a Linear board; lerp runs coding agents to move them across it. lerp init wires a repository to a Linear team, and running lerp opens the board that moves the work. There is no server, no scheduler and no store of lerp’s own.

What is in the box

The whole surface is the board plus two commands. Bare lerp opens the TUI, and the reconciling loop runs while it is open — N lanes, adopting live runs, reaping dead ones, repairing drift. Both panels are built, and the board’s only two write actions are the inbox’s promote and the work panel’s force-start . Beyond those, lerp init and lerp version complete the command line .

Everything else about a ticket still happens in Linear. Lerp reads the board, runs agents, and moves tickets between statuses; it does not compose comments, invent work items, or keep a queue of its own.

Where to start

Install is the binary and the two prerequisites lerp cannot satisfy for you. Quickstart is lerp init to a first promoted ticket. The board is the model underneath both, and SCOPE.md is the fence around the whole project — read that one before proposing a change.