The rabbit holes of building AI-native and agent systems.
Most people treat adtech and fintech as unrelated. Working the backend of both, they're the same architecture wearing two names, and that's the lens I read AI transparency claims through.
I've had 91 Trigger.dev tasks running my content and social pipelines. Most AI products are black boxes on purpose, so here's why I build on tooling that shows its work instead.
Circle just bought nearly a thousand blockchain patents from IBM. The framing is USDC protection; the real story is trust infrastructure for an economy where machines transact and nobody's checking IDs.
A bug in a Claude Code Stop hook got fixed four times, diagnosed correctly every time, and survived all four. The mechanism, the source-level regression test that catches it, and why a bug that keeps coming back is usually a missing decision rather than a missing note.
I gave a coding agent a guard that checks every commit lands in the repo and branch I intend. My 417 tests were all green. Then I hired a second agent to break it, and it walked through two holes the green suite never thought to check.
A video making the rounds argues graph engineering supersedes the loop-based agent pattern. After building multi-agent systems, I think the loop-versus-graph framing asks the wrong question. Topology decides whether you can SEE a failure, not whether one happens. Reliability lives in the deterministic checks at the edges, not in how you wire the agents.
Claude Desktop, Cowork, and Code look interchangeable. The real difference is what survives when the session ends, and that decides which one to build in.
For fifty years, controlling a computer meant sitting at it. AI coding agents broke that. Here''s how I drive my agents from my phone, what it actually costs, the local-vs-cloud distinction, and why this turns you from an operator into a conductor.