A nightly agent that plans ahead, with a logged undo and one-tap approvals
Chief of Staff
A nightly agent that plans ahead, does reversible work with a logged undo, and turns the rest into one-tap approvals. After beta feedback its predictions were widened to cover more tasks. Relaunching the mail client is the one action with no undo, and the public core in the repository makes no model calls.
Its parts
Dashed lines join each part to Chief of Staff.
- Model substitution: Finding the AI calls that do not need a frontier model.
- Drift testing: Testing whether browser agents still work when the web changes.
- Nightly note: A nightly note on what to do next, from one Opus call.
- Chief of staff actions: Five safe actions the chief of staff may take on its own.
- Follow-on: The next steps after a run finishes, queued while the context is fresh.
- Strategist: A Sunday deep dive that proposes builds and never starts them.
- Action log and undo: One log of every automatic action, with its undo written first.
- Polaris surfaces: Polaris screens for reading each system's dry run and its actions.
- Approval flags: A flag file per system that keeps it off until I approve it.
The launch film
How it works
How the night's signals become a note, a few safe actions and one log, with every part off until I review it. Select a part to open it.
Problem
The Life Tracker runs jobs overnight, and jobs fail. A failure used to wait for me to notice it. I wanted something to look over the night's runs first, mend the safe things, and tell me what is worth my attention, without being able to spend, send or delete anything on its own.
Approach
Three small systems share one rule. Each ships switched off and acts only once I create its flag file. Until then the chief of staff writes a dry run I can read, with no Opus call and no note, follow-on queues nothing, and the strategist runs only its pre-pass. Every action any of them takes goes into one shared log with its undo, written before the action happens.
Architecture
Three scheduled scripts share one action log. The chief of staff runs nightly, follow-on polls every 15 minutes and at the end of a session, and the strategist runs on Sundays. Polaris reads what they write.
What I built
The chief of staff runs daily at 02:30 and writes the note. It acts on a short whitelist and refuses anything outside it, such as mail, payments or accounts, logging the reason. Follow-on turns each finished run into the next steps. The strategist runs on Sunday for the deeper look. Polaris shows all three, plus one screen listing every action with an Undo button.
Since 14 October the whitelist also refreshes the calendar feed when it is over a day old and closes session threads it can show are done, 40 a night at most.
Public core and launch film
A runnable local core is public as version 0.1.0, released on 18 October. It keeps protected decisions, confirmed commitments and file evidence, and writes an attention report. It makes no model calls. The inbox, calendar and desktop integrations stay in my own installation.
The launch film above is a designed explanation of the workflow, with simplified example counts, and not a screen recording.
Results
With no flag, the chief of staff writes its dry run and nothing else, follow-on queues nothing and makes no call, and the strategist starts no session, so installing the jobs spends nothing and changes nothing. Turning one on is one file, and turning it off again is deleting that file. Undo is one command per action. I switched the chief of staff on for a live run from 02:30 on 14 October after a re-review passed it with conditions. Follow-on stays off while its redesign is built.
What didn't work
Some actions cannot be undone. Relaunching the mail client has no undo, so it is rate limited and logged as its own class. A queued brief can only be cancelled while it is still waiting.
Stack
- Python
- launchd
- Claude Opus
How these figures are sourced
The outcome figure is agent-reported: it is taken from a test log or report written by the agents that built and ran the system. The status was read from the Life Tracker session ledger, 13 October decision. Every figure and claim on this page is tied to a source file or a CV line in the site's content.