Docs Using easl
Reviewing work
Review what an agent changed in a changes tile, stage or discard it safely, undo any step, and read the evidence agents leave on the board.
All docs pages
An agent’s transcript stays in its terminal. Its work shows up on the board: a changes tile for the diff, code tiles and notes for the evidence, and an arrow path for the walkthrough.
The changes tile
File › Review Changes (⇧⌘R), or right-click the canvas › Review Changes, opens one view of what changed, file by file, for reviewing an agent’s work like a pull request. If a changes tile for the same folder and base is already on the board, easl goes to it instead. Agents create one to show you what they did.
- Added lines are green, removed lines red, shown as a unified diff with 3 lines of context. Each hunk is headed
Lines 15–46 · <function>. - A file list sits on top when there’s more than one file; click a file to jump to it.
/focuses the filter field to narrow files by path. - A Viewed box folds a file you’ve read until its diff changes. Deleted files start folded.
- Click a line to open it in a code tile beside the changes tile.
Pick the base
Click the summary at the top of the tile to choose what to compare against:
| Base | Shows |
|---|---|
| Uncommitted changes | Everything not in a commit yet, staged or not (the default) |
| Branch vs main | Everything the branch changed against its default branch: a pull request’s view |
| A commit or ref | Typed into the picker’s field |
The header names the comparison plainly, for example Uncommitted changes · 3 files · +40 −12. File › Review Branch opens the branch view directly. A changes tile can also review another worktree of the same repository; its title names the worktree.
Stage, unstage, discard
Per file, per hunk, or per selected lines (drag over a hunk’s lines, or ⇧-click one):
- Stage marks a change ready to go into the next commit (
git add). Unstage takes the mark off. Neither changes your files. - Discard throws an uncommitted change away from your files. It asks first: the button turns into a red Discard? for 3 seconds, and a second click discards. Then a notice says what went and how to get it back: “Discarded gui.md, lines 13–20 from your files · ⌘Z undoes”.
- Discard only puts back work not committed yet. A committed hunk (in a branch review) says committed and has no Discard button. There’s no discard-everything button, and reverting a commit is git’s job, not the review tile’s.
- A hunk shows staged once the index holds it, and partly staged if it changed again after you staged it.
Keys
Press Return (or click) to give the tile the keyboard; until then a tile key only tells you to.
| Key | Action |
|---|---|
| j / k or ↓ / ↑ | Next / previous hunk |
| J / K or ] / [ | Next / previous file |
| ↩ | Open the line in a code tile |
| s | Stage |
| u | Unstage |
| r, then r again within 2 s | Discard |
| m | Mention the hunk or selected lines |
| Esc | Clear a line selection, then give the keyboard back |
Undo tells you what it undid
⌘Z undoes the last change on the board, yours or an agent’s, and every undo or redo shows a notice naming it:
- “Undid omp: created 9 code tiles, 6 arrows · ⇧⌘Z redoes”
- “Undid Stage of src/regex_helper.rs · ⇧⌘Z redoes”
A Stage, Unstage or Discard is one ⌘Z step each, so a discarded hunk comes back exactly. While a terminal has the keyboard, ⌘Z belongs to the terminal and never reaches the canvas.
Evidence agents leave
- Captioned code tiles. An agent points at real code with a code tile and a one-line caption under its header saying why those lines matter. The range stays on its code as the file changes; “⚠︎ stale” in the header means that code is gone.
- Notes with live fences. A note’s excerpts render the real lines from disk, and a
proposefence shows a suggested change as a diff against the real code, then “✓ applied” once the file reads that way. See Tiles. - Walkthroughs. An agent joins its stops with next-step arrows, labelled like “1 · parse”. Select the first stop and press ⌥⌘→ to step through them in order; ⌘[ goes back a stop. See Navigation.
- Markers. An agent raises a pink attention marker on what it wants you to look at. It clears once you’ve seen it.
- “by
” in a title bar says which agent made a tile.
For presenting a review, Hide Canvas Chrome (⌥⌘T) hides the toolbar, tray, selection rings and markers.