Lem: a tall hooded figure holds one line, and four figures hang from it

Type a request in plain words, and get a pull request whose first line says green or not green.

Agents plan, build, test and review the change in your repository. Lem is a plugin for Claude Code that works closely with agterm.

claude plugin marketplace add pySilver/lem --scope project
claude plugin install lem@lem --scope project

Lem needs agterm. Run the two lines in your repository, then type /lem init.

The board of all tasks: a sidebar with five things that wait for you, and four columns of task cards
The same board on a phone: the column Waits for you, with three task cards
The board on a computer and on a phone. The pictures show demo data.

01 · The board

Every task in one place, on every screen

The board puts each task in a column by who acts next, and it updates by itself. The same board opens in agterm, in a browser and on your phone.

A task opens with five tabs: Overview Criteria and decisions Checks and review Timeline Artifacts

02 · How a task goes

Two tracks to one pull request

Lem reads each request, and tells you its type and its track in one line.

Fast track

  1. Your request
  2. One builder makes the change
  3. Checks and one read
  4. Pull request the merge agent reads it
  5. Merge when the merge agent calls you

Standard track

  1. Your request
  2. Interview you answer
  3. Acceptance criteria you say yes
  4. Plan and build a builder for each part
  5. Checks and a review
  6. Pull request the merge agent reads it
  7. Merge when the merge agent calls you

You can act here.

Each request opens a task in an agterm session of its own. The fast track is for one plain change with no open question: a typo, a rename, the fix of one rule. One builder makes it, and nothing waits for you. When another person wrote the ticket, its one criterion waits for your yes first.

The standard track is for every other request. The interview runs in the session of the task, one question at a time, each with its guess. Nothing builds before your yes to the acceptance criteria, unless you are away or the task runs at night. Then the pull request is not green.

The build asks you nothing. A ladder of agents decides each choice, and the pull request lists each one with its reason. Only a circuit breaker stops a task, with a document for you.

A fresh merge agent reads each pull request. It merges a green one that is not careful, and calls you for the rest.

you /lem the footer says Terms, not Terms and Conditions

lem docs: "the footer says Terms". Fast track: one builder, the checks, one read, then the pull request. Nothing waits for you.

lem The pull request is open. Green. The merge agent found nothing for you, and Lem merged it.

An illustration of a request on the fast track.

you /lem the export holds the gift note of an order

lem An order with two notes: both in one cell, with a semicolon? My guess: yes.

you yes

lem The acceptance criteria, which two personas read:

1. Order 1042 with the note "for Ania" has that text in its row.

2. An order with no note has an empty cell.

you yes

An illustration of the interview of a request on the standard track, in the session of its task.

03 · On your phone

Follow the work away from your desk

The board opens on your phone through Tailscale, a private network of your own devices. Only your Tailscale login gets access.

Add the board to the Home Screen. Lem then sends a notification each time something starts to wait for you.

Two computers, one address. /lem serve join HOST shows the repositories of a second computer on the board of the first.

The computer must be awake. Lem needs Tailscale only for another device.

Set it up one time

  1. Install Tailscale on the computer and on the phone, with one account.
  2. In the Tailscale admin console, turn on MagicDNS and HTTPS.
  3. Type /lem serve tailscale in Claude Code.
  4. On the phone, open the address that Lem gives, and select "Add to Home Screen".
  5. Open Lem from the Home Screen, and turn on notifications with one tap.

The board on your phone, step by step

04 · Many tasks at once

Many tasks build and land at the same time

Each task has its own worktree. A task waits for another task only when it needs the result of that task, or when you put that task first.

Green, or not green with each reason

The first line of each pull request says green or not green. A pull request is not green when, for example:

  • your tests got less strict;
  • the review left a must-fix after two rounds;
  • a criterion changed during the build;
  • a decision went past the personas.

With branch.land = "owner", you merge each pull request. Green means you can merge without a read.

The panel of a task whose merge review calls you: the review is the first card of its Overview, and the pull request is not green
A task whose merge review calls you, on its Overview. The picture shows demo data.

05 · Install

Start in your repository

At the root of your repository:

claude plugin marketplace add pySilver/lem --scope project
claude plugin install lem@lem --scope project

Then start Claude Code in agterm there, and type /lem init. Answer three questions, read Lem's page, and type "land". Then type your first request.

Install lists every tool that Lem needs, and /lem init checks each one. The main tools:

  • agterm
  • Claude Code
  • git
  • Python 3.11 or newer
  • revmux
  • cronn
  • GitHub CLI
  • Codex, highly recommended
  • Tailscale, for your phone

Lem keeps its settings in the .lem/ folder of your repository, in git. To remove Lem, follow the steps in Remove.