← Back to The Lab
Chief.
a personal capture-triage-action pipeline
Chief of Staff is a personal AI agent system I designed, built, and run — currently in a
friends-and-family pilot with real invited users, not a prototype. Send it anything
(a to-do, an idea, a reminder, a note, an event) by text or email, and an agent
classifies, sorts, and routes it into an organized hub — no fields, no categories,
no manual triage.
Claude Haiku triage engine — v9
Supabase + Postgres RLS
Cloudflare Workers (email ingestion)
PWA + Web Push
Scheduled health monitoring
What's actually running underneath it
Built solo, iterated in production. This is the piece I'd point to first if asked how I use AI day to day.
Triage engine. A Supabase Edge Function calls Claude Haiku against an explicit rule set — priority, a life-domain category taxonomy (Work/Home/Health/Finance/Family/Errands), and effort (quick/medium/big) — plus a splitting rule that turns one multi-item capture into several linked rows.
Named, versioned agents. The triage engine is on its 9th revision; the push-notification agent is on its 6th. Each ships independently, with its own changelog — not a black box that gets re-prompted until it works.
Real intake, not a form. Capture happens via a text box or a personal forwarding email address per user, routed through Cloudflare Workers with an unknown-sender approval flow — no manual account setup per person.
Production discipline. Scheduled health checks catch staleness before a user notices; a Postgres trigger and RLS policies keep multi-user data isolated without a custom auth system.
Governance instinct. Multi-user readiness was scoped deliberately in three buckets (data isolation, email intake, OAuth) rather than opened all at once — the same instinct I'd bring to evaluating what actually gets automated versus what stays manual.
Cost-aware by design. Runs on free-tier infrastructure plus prepaid API credit — no service can silently overspend, because none has a card on file that allows it.
The core loop, screen by screen
Rebuilt from the app's real design tokens (ink/panel/brass palette, Archivo + IBM Plex Mono, 14px radius) — same layout and content as the walkthrough I use with pilot testers.
01 · Cold open
One place to capture everything on your mind — the hub, at rest.
02 · Capture it
Chief.
"finish bathroom: paint, floor vent, shades"
Capture
or forward an email to your capture address —
No categories, no fields, no friction. Type it or forward it.
03 · Triage
sorting via Claude Haiku…
An agent reads it and figures out type, priority, category, and effort — usually within a few minutes. One capture ("finish bathroom…") becomes a project plus three linked to-dos.
04 · Sorted into the hub
Everything lands already broken out by type — no manual filing.
05 · Today banner
Chief.
⚑ Today & overdue (3)
Paint bathroom trimdue
Call dentist — rescheduledue
Send Q3 budget docoverdue
Time-sensitive items get pushed to the top so due dates don't get lost in the queue.
06 · Swipe to complete
Chief.
Paint bathroom trim✓ done
Call dentist — rescheduledue
Send Q3 budget docoverdue
One gesture — done, archived, out of your head. Same swipe everywhere in the app.
07 · Suggested calendar event
Chief.
Dentist reschedule callevent
Add to calendar
Dentist — reschedule call
Thu · 2:00–2:30 PM
Add
One tap sends event details straight to your phone's calendar, already filled in.
08 · Settings — capture email
Chief.
Your capture email
capture+tyler@tylerweed.com
Copy
Forward anything to this address and it lands in your queue like anything else.
Every user gets a personal capture address — no OAuth, no per-person setup.
09 · End card
Chief.
Capture anything. Get it sorted.
Solo-built, real pilot users, running today.
Want to try it?
Chief of Staff is running a private pilot right now — real invited users, not a prototype. I'm still adding testers. If you want an account, get in touch and I'll set one up.
Get in touch →