All docs
Start
Introduction
What aiL is, what it solves, and what it is made of.
aiL is a personal agent system. You do three things: propose, decide and accept. The rest of the work is done by the coding agents on your own machines, and the system takes care of dispatch, hand-offs, review, merging and record-keeping.
The name and the domain come from the same sentence: art is Long, from the Latin proverb Ars longa, vita brevis. Its Chinese counterpart is Zhuangzi's “My life has a limit; knowledge has none.” Life is short, so long work should not occupy a person.
What it solves
Anyone who works with several coding agents on several machines soon meets the same problems:
- Every agent has its own way of working, and sessions are scattered across terminals on different machines. You have to remember what is where.
- One piece of work goes through "do, review, revise, merge", and a person carries the messages between every step.
- When an agent finishes or gets stuck, there is no single place to see it.
aiL gathers this in one place. One Agent Desk is connected to each of your machines, and a Daemon on each machine starts agent sessions for it. You say one sentence to the Router; the system carries the work through its workflow and comes to you only when a decision or an acceptance is yours.
What it is made of
There is one executable per platform, ail, with three uses:
| Use | What it is |
|---|---|
ail desk |
The Agent Desk: UI, engine and database. One per person |
ail daemon |
The Client Daemon: one per machine, dialling out to the Desk |
ail <subcommand> |
The command line that agents use inside a session and you use in a terminal |
Agent programs are called harnesses. aiL starts them over ACP (Agent Client Protocol) and currently supports five: claude, codex, dsh, pi and antigravity. To the engine and the UI, every session they produce is the same Worker.
What gets done and how it flows is decided by plugins in Git: roles, workflows, the UI and repository registrations are files, and changing them takes effect without a new binary.
How one piece of work gets done
- You tell the Router what you want. The Router only decides the intent and the repository, then dispatches.
- The engine creates a run and starts a Worker on the machine the role is bound to.
- The Worker works in its own Git worktree. When it needs a decision, it pushes a Review Report and you answer on the Desk.
- A gated step is reviewed by a second Worker. After a pass, the engine merges the change, archives the task and writes a Journal entry.
- The run ends and stays on the board with its debrief until you archive it.
The rules for each step are in Workflows and the engine.
The UI
The Desk UI is a desktop in the browser:
- Board: one card per run, grouped into Needs you, In conversation, In progress, To archive and Ended.
- Session page: one page per session, like a chat window, with streaming replies, tool-call records, follow-ups and image attachments.
- New session page: pick a machine, a folder and a harness to open a session directly, or open a PowerShell or Bash console.
- Reports: the review and presentation reports that Workers push, switched by name and version.
- Config page: pairing and authorization of machines, the main repository, repository registrations, and the binding of roles to models.
Below 1024 pixels the three columns become three full pages you swipe between, so it works on a phone.
Status
aiL is under development. Binaries and source are not public yet. These docs describe its current design and usage.
Where to start: read Concepts for the vocabulary, then the Methodology for why it is designed this way.