docs menu: agents
docsstart
agents
Which agent CLIs report to easl, their setup, and what survives a quit or reboot.
on this page
Any terminal program runs in a tile. Integrated agents add:
- a lifecycle dot on their tile
- a follow tile that tracks their reads and edits
- your mentions in their next prompt
which agents report what
| Agent | Setup | Lifecycle dot | Mentions in your prompt |
|---|---|---|---|
| omp | One symlink (below) | working, blocked, done | Yes |
| Claude Code | None, inside easl | working, blocked, done | Yes |
| Codex | None, inside easl | working, blocked, done | Yes |
| opencode | None, inside easl | working, blocked, done | Yes |
| Gemini CLI before 0.60 | None, inside easl | working, blocked, done | Yes |
| Gemini CLI 0.60 and later | None | None: plain terminal | Hyper-V paste |
| aider | None (easl’s aider wrapper) |
done only | Hyper-V paste |
| Any other CLI | None | done only, via notification or bell | Hyper-V paste |
omp
omp is the first-class agent. Install easl’s omp extension once:
mkdir -p ~/.omp/agent/extensions
ln -sf /Applications/easl.app/Contents/Resources/extensions/omp/easl.ts ~/.omp/agent/extensions/easl.ts
In a tile, omp then gets the full integration and the easl skill. An approval prompt turns it blocked.
claude code and codex
Inside an easl tile, claude and codex get omp’s integration. easl’s wrappers, first on the tile’s PATH, start the real program with per-session hooks and the easl skill.
- Nothing touches your global agent config. Claude Code loads easl’s plugin per session. Codex’s hooks are a per-session override. easl never writes them to
~/.codex. - Codex shows blocked at launch while it asks whether to trust the folder.
- A mid-turn question turns the tile blocked, with the question in its bubble, even with approvals off (
--dangerously-skip-permissions,--yolo). Answering sets it back to working. - Codex’s
workspace-writesandbox blocks the easl socket, so Codex runseaslwith escalated permission. It asks once: choose “don’t ask again for commands that start witheasl” and it stops asking, in later sessions too. - Set
EASL_AGENT_HOOKS=0in the tile to turn the integration off.
opencode and gemini cli
Both run with self-update off.
- opencode gets easl’s plugin. Blocked means a permission request or a question. Answering sets it back to working.
- Gemini CLI gets easl’s hooks as a settings layer merged with yours.
Gemini CLI 0.60 and later refuses that layer and runs as a plain terminal.
aider and other clis
easl’s aider wrapper turns on aider’s notifications, so the tile goes green (done) whenever aider waits for you. No dot while it works, never blue or orange: read its screen for a y/n question.
Any other CLI works the same way if it sends a terminal notification (OSC 9 or OSC 777) or rings the bell in the foreground. At a shell prompt, the tile gets an attention marker instead.
Paste mentions as text with Hyper-V (⌃⌥⇧⌘V): see mentions.
states and ⌘J
| State | Dot | What you see |
|---|---|---|
| working | Blue | Busy. |
| blocked | Orange | A ring and ✋ bubble with its message (“approve Edit?”). Off screen, an edge pill points at it. Click the bubble to answer in its terminal. |
| done | Green | Finished, not yet seen. |
| idle | Grey | Waiting for your next prompt. |
Seeing a done agent turns it idle: focus its terminal, or leave it visible at readable zoom for a few seconds.
- ⌘J (View › Go to Next Needs-You) steps through blocked agents, then marked tiles, then unseen done agents, each in reading order. With nothing pending, it says “Nothing needs you”.
- A board’s tab shows an orange dot for a blocked agent, green for an unseen done one.
- If easl isn’t frontmost, finishing or blocking fires a macOS notification.
- Go to (⌘P) lists them first.
what agents make
An agent’s objects land next to its terminal, clear of other tiles, inside your view when there’s room nearby. Their title bar says “by <terminal name>”. The view never moves by itself: look for a marker, or press ⌘9.
⌘Z undoes agents’ changes too, one batch per step, and says so: “Undid omp: created 9 code tiles, 6 arrows · ⇧⌘Z redoes”. When a terminal has the keyboard, ⌘Z goes to it.
quitting, closing and rebooting
- Quitting easl ends nothing. Terminals live in zmx sessions: they survive a quit, a crash or a rebuild, and return when you reopen the folder. Closing a tab or window with terminals asks: Keep Running, End Sessions or Cancel. Closing the last window quits easl, and the sheet says so.
- An agent that finishes while easl is closed returns done (or blocked) with its answer.
- After a reboot, omp, Claude Code and Codex tiles relaunch with their recorded session:
omp --resume=<id>,claude --resume <id>,codex resume <id>. - Closing a terminal tile ends its session. The close sheet names what ends (“omp and 1 background process”). Cancel is the default; ⌘⌫ closes. ⌘Z brings the tile back with a new session.
Outside the app, use zmx list and zmx kill. See troubleshooting and uninstall.