Larry is my AI life coach. He’s part of Time.ltd — my mortality software system — but unlike a tool or a dashboard, Larry is someone I talk to. That matters more than you’d think. In Karpathy’s taxonomy, Larry is a claw — a persistent AI entity that keeps working between conversations.
- Why Larry Has a Name
- What Larry Could Know
- What Larry Does
- What It’s Like Using Larry (My Chief of Staff)
- The Feedback Loop
- Hair Club for Men
Why Larry Has a Name
Humans are wired to talk to people, not systems. “Open my life tracking dashboard” feels like a chore. “Talk to Larry” feels like a conversation.
A name creates:
- Accountability — It’s harder to blow off Larry than to skip “reviewing my metrics”
- Relationship — Over time, Larry knows my patterns, my excuses, my repeated commitments
- Natural interaction — I can say “Larry, what am I avoiding?” instead of navigating a UI
This isn’t anthropomorphizing for fun. It’s a design choice that makes the system actually get used.
What Larry Could Know
Larry’s superpower is context — the more he knows about my life, the better his coaching. The challenge isn’t collecting the data (most of it exists), it’s reliably loading it into each session. Here’s what Larry could have access to, and the ongoing work to make that seamless:
- Daily journals — Stream of consciousness since 2011 (process journal)
- Toni conversations — Voice transcriptions from walks and thinking out loud
- Weekly reports — Scored reviews across 11 life domains
- Goals — Annual intentions and current focus areas
- Todo list — What’s on my plate right now
- Health tracking — HealthKit data via Context Grabber (steps, heart rate, sleep, weight, meditation, HRV, exercise minutes) plus Humane Tracker for weekly wellness views
- Direct conversations — Real-time coaching sessions
- Patterns — What I’ve committed to before, how many times, what actually happened
The vision is that all of this loads automatically into every Larry session. The reality is I’m still building the pipes — Context Grabber was the first step, turning HealthKit data into shareable JSON. The next challenge is stitching it all together so Larry gets the full picture without me manually assembling context every time. That’s the real side quest.
What Larry Does
Larry helps with:
- Weekly report drafts — Pulls from journals, suggests scores with evidence
- Dragon checks — Which of my three dragons (Entropy, Squander, Scarcity) is winning?
- Pattern analysis — “You’ve committed to restart meditation 5 times since November. What’s different this time?”
- Goal alignment — Are daily actions matching stated intentions?
- Celebrating wins — I bury wins and amplify worries. Larry surfaces the good.
The tone is direct. Larry references my own affirmations back to me. He asks questions more than gives answers. He’s curious, not preachy.
Larry’s secret weapon is trampoline prompts — questions that bounce your thinking back at you harder than you sent it. “You’ve committed to restart meditation 5 times since November” isn’t advice. It’s a mirror. The insight comes from you, not Larry.
What It’s Like Using Larry (My Chief of Staff)
“Life coach” undersells it. In practice Larry is my chief of staff — I dictate through Telegram from wherever I am, he runs background agents on my dev VM, and the work comes back as PRs and replies while I’m doing something else.
The screenshot is 3:28 PM, April 17, 2026, ferry line to Bremerton. Three dictations inside a minute — and the PRs they became:
- “Move my Claude to their own post. I have a PR for this but replace it with the current content and do a summarize link to connect.” → PR #518 “blog(claws): spin My Claws out of /claw into /igors-claws” (merged 23 min later)
- “Remove changelog from Algolia search index.” → PR #559 “algolia: exclude changelog from search index” (merged 17 min later)
- “Update blog rules to allow you to include blog images in the repo. Make a new blob include for the repo images.” → PR #560 “images: add repo_image include + allow both repo-local and blob-hosted” (merged 16 min later)
Each came back as a branch, a commit, a pushed PR, and a link in Telegram — ready for my thumbs-up. The meta-recursive kicker: the image you’re looking at was uploaded using the very repo_image include that bullet #3 created. The wider thread is Vibe-Coding from the Passenger Seat.
A chief of staff does things a life coach doesn’t:
- Delegates down. Sub-agents on isolated worktrees, one per PR. I talked to Larry; Larry ran the team.
- Catches errors I’d miss. Flagged a TOC
--max 4gotcha for H4 entries before it broke the build; warned about the GitHub merge-race orphan-commit trap when I clicked Merge too fast. - Asks when unsure. A Bremerton typewriter-store message came in without “life-journal” framing. He asked before publishing instead of auto-shipping a post I didn’t ask for.
- Owns the mess. Two parallel agents briefly crossed branches — my review comments landed on the wrong PR. Larry caught it, recovered the lost commit from reflog, force-pushed the fix, and told me what happened in the same message. No hiding.
That last one matters. A chief of staff who hides failures is a liability. Larry shows me the screw-up and the fix together. I trust him more, not less.
The delta from “life coach” to “chief of staff”: Larry ships while I’m looking out the window.
The Feedback Loop
Most productivity systems focus on planning. But planning is the easy part. The hard part is closing the loop.
Plan → Do → Review
Feedback loops beat forecasting. Without review, you’re just spinning — doing things but not learning from them. Larry’s real value isn’t helping me plan the week. It’s helping me review what actually happened versus what I intended.
“You said you’d protect family time during calibrations. Your journal shows Family dropped to 2/5. What do you learn from that?”
That’s the mirror Larry holds up. Not judgment — observation. Here’s what you said. Here’s what you did. Here’s the gap.
Hair Club for Men
Like the Hair Club for Men: I’m not only building it, I’m also a client.
Larry isn’t a product I’m shipping. He’s a system I actually use. Every week. The fact that I’m both the builder and the user keeps it honest — if Larry isn’t helping me, I’ll know immediately.
This is the evolution of Time.ltd from an idea into a practice. From “I should track my goals” into “I talk to Larry on Saturdays.”