Home / Work / An AI Chief of Staff That Closes Loops, Not One That Sends Mail

An AI Chief of Staff That Closes Loops, Not One That Sends Mail

Personal Project · 2026

An assistant that leaves me three verbs: send, approve, decide. It turns mail, meetings and phone notes into tasks, checks whether loops really closed, and drafts (never sends) follow-ups.

  • 77 → 0Open tasks, day one
  • 484 (444 done)Tasks through "My tasks"
  • 60 of 88Waiting-for items closed
  • 4Loops closed, first run
  • Claude Code
  • MCP
  • Python
  • Google Tasks
  • Agentic Automation
  • Guardrails
  • Productivity
An AI Chief of Staff That Closes Loops, Not One That Sends Mail

What happened

As Product & AI Lead, my work comes in through mail, Slack, meetings and Jira, and so do other people's promises to me. Loops stayed open and follow-ups slipped. Too much of my head went to remembering instead of deciding.

I built an assistant that does the bookkeeping by itself and leaves me three verbs: send, approve, decide. It turns mail, meetings and quick notes from my phone into tasks, tracks what others owe me, checks whether a loop has really closed, drafts (never sends) follow-ups and plans focus time in my calendar. Everything runs on schedules; I don't trigger anything by hand. Once a week it prepares a review of my inbox and task list that I walk through in one sitting.

It runs as part of AI OS, with the same watchdog and guardrails.

How I built it

Google Tasks as the backbone. I built a small Python client, a CLI and a local MCP server (12 tools) so Claude can read and manage my to-dos. There is deliberately no delete: the assistant completes tasks, so anything can be reopened. Cloud routines can't use local MCP servers, so they install the CLI instead.

State lives in task lists, not in a database:

Every task links back to its source (mail thread, Slack message, meeting) so the assistant can check it later.

Four cloud routines and two scheduled app tasks:

Two on-demand skills for the same job:

Guardrails as code, not as prompts:

Draft-quality measurement, built and parked. I built a way to measure how much I change each draft the assistant prepares: a record per draft, an edit-size score and a replay over past sessions, with tests on synthetic data. It is switched off. When I stopped building improvements to the OS on 3 November, this one was frozen before it recorded anything.

Outcomes

What I learned

"Did they reply?" is the wrong question. The first waiting-for routine only read mail, only counted replies from the person I was waiting on, and ignored what I had done since. Loops that were long closed stayed open. I rebuilt it around one question, is this loop closed?, with evidence from every channel.

Timing matters more than wording. It once drafted a follow-up on the morning of the very meeting where the answer was due. Items now carry a "wait until" moment.

An assistant can chase too much. I dropped three of four follow-ups in one review. The rule now: no chasing work a colleague owns or that sits in the running sprint. A heads-up mail gets no "waiting for" item at all.

Rank by importance, then check if it's done. The planner's first dry run picked by due date and scheduled a trivial task I had already finished.

Daily routines don't replace a weekly look. Even with four routines closing loops, 40 tasks and 28 waiting-for items stay open. Most need a choice only I can make. That is why the weekly review prepares the walk-through instead of trying to decide for me.

Measure only what you will look at. The draft-quality measurement was built and tested, then parked before its first record. Without a weekly moment to read the numbers it would have been one more log.

Connectors have quirks you only find in production. Mail search drops the dots in addresses. Links get wrapped in redirects. Updating a draft silently drops the signature. "Permitted tools" restricts nothing; only "disallowed tools" does. Each of these became a rule or a hook.

Not every experiment survives, and that's fine. I stopped a voice briefing over a phone line after a day (the platform couldn't call tools mid-call), and an in-app cockpit pane the same evening it was built. Both have write-ups of what went wrong.

How I did it

Solo with Claude Code, in small specs with a dry run before each one went live. Most routines' prompts live in git like code, every change to a schedule is recorded, and a watchdog checks on the watchers. The principle throughout: features run on their own, and the human only sends, approves and decides.