Version 1.3.0 · A control tower watches over each project
lab tower <project> opens a tower that checks in every 30 minutes and tells you what each lane is waiting for from you: a question, a permission, an acceptance ready or a blocked lane alerts its tab.
A lane can become permanent: it chains its batches and never goes to acceptance or gets closed.
A batch with a measurement that can only happen at a later date is delivered anyway, then reopened on its own at that date.
A Claude window that hits its limit restarts in its tab on the next account, each login checked by a real call.
The Cloud test suite fits your plan and falls back to the Mac when the plan is full; services of closed lanes are reported and stopped in one command.
Version 1.2.5 · Sessions restarted all at once each keep their lane
When cmux reopens dozens of sessions at once, none is wrongly told “update in progress” any more: a session that starts alongside the others works normally and takes its lane lock at its first tool.
A live session in a lane without a lock is named: lab status shows it, lab next refuses to open a second session on the same files, and lab doctor tells you what to do.
A real update keeps its message: start nothing until it has finished.
Version 1.2.1 · Closing work that is already delivered no longer trips over the main branch
When your pull request is already merged and your copy then pulled the main branch, lab close no longer refuses the files that came from that branch: they are already delivered, and one line tells you how many were set aside.
A file that really differs from the main branch stays protected: closing stops and names it.
Offline, the real close stops and keeps the folder instead of judging from an old copy.
Version 1.2.0 · A tidy menu bar, and Cloud agents that hold on
A chevron in the menu bar hides the other apps’ icons behind it and tells you when a new app shows up or the order has moved.
lab widget order save remembers the order of your icons and lab widget order apply restores it; lab widget tidy tightens the spacing and hides duplicates; lab widget remove undoes it all.
On a Cloud machine, a command that eats all the memory is stopped on its own: your agent goes on with its batch instead of going down with it.
An agent stopped on its Cloud machine, or a paused machine, is reported with its cause by lab next instead of leaving the batch waiting.
Version 1.1.1 · Closing work delivered in two steps now goes all the way
When your last batch was delivered by two stacked pull requests and your local copy followed the main branch afterwards, lab close now removes the folder and branches instead of stopping on “remote branch changed”.
A remote branch that really carries new work stays protected: closing stops and keeps it.
A folder left open by this issue closes when you type lab close again.
Version 1.1.0 · Your Mac at a glance, and accounts that no longer lock up by mistake
lab top shows each of your agent’s sessions tied to its project, the memory state and what can be cut safely; lab widget install puts it in the menu bar, with six system modules (processor, memory, disks, network, battery, temperatures).
Claude account rotation records the account actually signed in: an account with usage left is no longer marked exhausted, the wait stops cleanly with Ctrl-C, and lab account free clears a wrong note.
lab close also closes the tabs and processes left in the closed folder, accepts a last batch delivered by two stacked pull requests, and finds a pull request merged by hand.
lab mcp measures your agent’s tool servers and pins their version on request; lab doctor warns above 1 GB.
lab sweep is up to three times faster with many working folders, and Cloud mode picks on its own, batch by batch, between a remote machine and your Mac.
Version 1.0.1 · Merging no longer waits for a job that will never run
When a pull request is marked ready and a job is skipped by its own condition (a deployment limited to main, for example), lab merge merges it as soon as the rest is green, instead of waiting three hours.
If a job reserved for ready pull requests can no longer run because the workflow does not listen to ready_for_review, lab merge stops right away and says what to do: add ready_for_review to the pull_request types, or push a commit.
lab doctor reports this setup ahead of time.
A watcher already waiting resumes when you type lab merge again.
Version 1.0.0 · Treelab speaks English
The lab command, its messages, its refusals and the website installer are in English, like the instructions given to your agent, the context handed over at the start of each session and the KEY=value lines it prints.
Your agent answers in your Mac’s language, then in the language you use with it.
The former French command names are still accepted, and lab help glossary gives each English word with its former French equivalent.
Your existing projects carry on unchanged: their French documents and whatever lab had already written on your disk are still read as they are.
The licence and terms of sale move to version 2026-10-15.1, which describes a package in English; lab update installs this version like the previous ones.
Version 0.9.2 · Founder places shown, simpler withdrawal
The “Founder pack” card on treelab.sh shows how many of the 20 places are left, based on sales actually paid, and says when the offer is sold out.
A purchase made from the terminal can be withdrawn through the personal link sent with your key: the key is revoked, the refund follows and you receive a confirmation.
The lab command is unchanged: nothing to do on your side, lab update installs this version like the previous ones.
Version 0.9.1 · What’s new, online sooner
Each new version appears sooner on treelab.sh, its what’s-new pages and its Atom feed: a version already checked is no longer re-verified in full before going live.
The lab command is unchanged: nothing to do on your side, lab update installs this version like the previous ones.
Version 0.9.0 · Parallel work without loss
Where several sessions share the same git index, a git commit without paths or an overly broad git add is refused, with the safe command instead.
A database migration that reuses a number already taken is refused before merging, with the next free number; applying it remotely is refused outside the main branch.
lab close --dry-run lists every obstacle before closing, and lab recette records approval or refusal after a trial.
When lab update fails, it names the reason and the file involved.
Buying from the terminal: the install script creates the order for the chosen offer, follows the payment for 30 minutes and accepts the key pasted from the e-mail.
Version 0.8.2 · Stricter reviews
The end-of-batch review also reports a weakened test, scope creep and needless complexity.
Verification gives one verdict per completion criterion: passed, failed or to be checked.
Upgrading with lab update still works from 0.8.0 and earlier versions.
Version 0.8.1 · Update fixed with Codex
lab update failed silently on machines with Codex installed: upgrading works again.
The review agents generated for Codex are now updated without blocking during later upgrades.
Version 0.8.0 · Simpler purchase, finer checks
Payment fits on a single page; the confirmation e-mail arrives in your country’s language, with the licence key first and no attachment.
The key is sent as soon as you pay; a withdrawal revokes it.
The setup assistant offers Claude Code first and explains what to do if you paste a fingerprint instead of the key.
lab doctor flags a batch that weakens its tests without a written reason, and any completion criterion never cited as proven.
git checkout -b is no longer wrongly refused by the guardrails.