Vita brevis
Life is short
Your attention is the bottleneck.
You propose, decide and accept. Sessions, machines and worktrees are implementation details: one Desk shows everything that needs you, and nothing else interrupts.
Read「Methodology」art is Long
The craft is long; a life is short.
aiL is a personal agent system. You propose, decide and accept. The long work goes to the coding agents on your own machines, and the system dispatches, hands off, reviews and merges without you watching.
One run
Say one sentence to the Router and go do something else. Dispatch, hand-offs, wake-ups, review, merge and archive are certain steps, so the engine executes them from the workflow without spending your attention.
When a Worker needs a decision, it pushes a Review Report to the Desk. You answer from your phone and it carries on.
Example · implement workflowr261121-010214-3fa9
ail dispatch --repo billing --intent implementstudio-pc (codex)ail worktree start 261121-csv-export, then works in its own worktreeail report ask: export every column, or only the visible ones?progress, wake in 10 minutesreadyverdict: changes, two itemsready againverdict: pass3 h 03 min · 15 events · 3 of them yours
The whole aphorism
Vita brevis, ars longa, occasio praeceps, experimentum periculosum, iudicium difficile.
Life is short, the craft long, opportunity fleeting, experiment perilous, judgment difficult.
The proverb is only the first two clauses. aiL is designed as an answer to all five.
Life is short
Your attention is the bottleneck.
You propose, decide and accept. Sessions, machines and worktrees are implementation details: one Desk shows everything that needs you, and nothing else interrupts.
Read「Methodology」The craft is long
Long work goes to Workers, asynchronously.
Dispatch returns at once and results arrive as new messages. A Worker that has to wait says when to be woken, and the engine wakes it. Context lives in Git; the runtime can be replaced wholesale.
Read「Workflows and the engine」Opportunity is fleeting
Dispatch the moment you think of it, from anywhere.
From a phone, a laptop or a terminal, start a session on any machine you have connected. An agent on one machine can run PowerShell or Bash on another and get a structured result back.
Read「Across machines」Experiment is perilous
Every attempt is isolated and reviewed.
Changes are made in their own Git worktree. A gated step is reviewed by a second Worker, and the engine merges only after it passes. Unverified assumptions get a prototype before a plan.
Read「The Worker contract」Judgment is difficult
Judgment is kept for the people and moments that need it.
The Router only decides intent and repository. Hand-offs, merges and archiving are certain, so code does them, not a model. When the call is yours, a Worker pushes a Review Report and continues once you answer.
Read「Router」Anatomy
One ail ships per platform. It runs as the Desk, as a Daemon, and as the command line that agents and you both use.
ail deskUI, engine, databaseail daemonone per machineThe third use is the command line: agents in their session shell and you in a terminal use the same ail subcommands to get things done through the Desk.
Every session the engine and the UI see is the same Worker. What differs between the five harnesses is a record of data; no code branches on a name.
The Worker contractWhere a harness runs and where its files live are two separate things. A repository on a machine with no harness is edited by an agent running on another.
Across machinesRoles, workflows, the UI and repository registrations are files in Git. Changes take effect without a new binary.
PluginsConversations, run logs and reports are persisted by the Desk, never replayed from a harness; the Journal is a file in your own main repository.
ArchitectureDocs
aiL is not public yet. Start with the concepts and the method, then read each contract.
My life has a limit; knowledge has none.
To chase the limitless with the limited is perilous.
So don’t chase it yourself.
aiL 0.1.2 is under development. Binaries and source are not public yet.