Building AI agents at Saint · ClawCon London 2026
Four things I’ve learned building delightful always‑listening agents.
Disclaimer: I only learned I was talking today!
I’m Daniel Hails. I’ve been building AI agents at Saint.work.
In 2013, Carrascal et al. asked 168 people what they’d accept for their browsing history.
The median price. The cost of a Big Mac.
Last night, 23:03
An agent we’re building at Saint skipped the negotiation for me.
Two
What I build for at Saint: the system noticing what I didn’t ask about.
Blips of salience
A self-authored life is built from the things you notice.
Three — For everyone else
You’re at a lobster‑themed personal‑AI festival on a Wednesday night.
…and neither am I
…and a slog of unglamorous plumbing
Blast‑radius control
A bad tool call can’t nuke the machine, leak the filesystem, or reach a network it shouldn’t.
Ambient credentials
The agent uses my Stripe, GitHub, and Google Drive without ever seeing the real keys. The proxy signs requests; the agent sees capabilities.
Per‑persona files
Mum’s finances and my work repos live on different rungs of the same ladder. Agents cross rungs only on explicit request.
Four
An agent needs…
Anything less is a chatbot in a trenchcoat.
Wrap — Agent‑to‑agent
While I was on the train here, the agents I build at Saint shipped 19 issues, 11 PRs, and 8 closes. Meet Ava, our first-person agent, and Iris, her sibling. When Ava needed to test a permission escalation, she didn’t call an API — she messaged Iris. On WhatsApp. With a phone number. No new protocol, no new standard, no new committee — the substrate has worked since 1992.
Four rules for the lobster in your pocket