We just open sourced an AI that places real phone calls on your behalf. We named it after the dog.

Quick roadmap:

• Meet the actual Banjo, and why the name isn’t just a cute mascot choice
• What the software does, in one real example
• Five ways the dog’s actual personality shows up in the architecture
• Two bugs that made it to a live phone call before we caught them
• What’s still held together with tape, said plainly
• How to run it yourself

Meet Banjo

Banjo is a rescue terrier mix. Nobody in the family agreed on his exact breed mix and everyone agreed on the verdict: the little terrier with the big personality. He has ears that stand up like he’s perpetually mid-question and a face that looks skeptical of your plans by default. There’s a photo of him in a pirate costume on the beach in Asbury Park, standing his ground against wind that’s actively trying to remove his hat. He did not ask for the costume. He tolerated it, the way he tolerates most indignities, with visible reservations and zero actual protest.

Subtitle: On the dark psychology of token scarcity, the $200 plan that still isn’t enough, and why Anthropic’s usage bar is the most stressful thing on the internet

It’s 11:47 a.m. on a Saturday and I am staring at a message in my beloved terminal that has become the most familiar sentence in my life:

Here’s what nobody tells you about AI coding assistants: you’re still coding the old way.

Quick roadmap:

• Why “copilot mode” is already obsolete
• Two real projects built with agentic coding (native iOS app + retro game)
• The three shifts that separate traditional coding from agentic development
• How AI collaborates on architecture and PRDs using plan mode
• What actually happens when AI owns the implementation layer

The Uncomfortable Truth About Copilot Mode

For the past two years, we’ve been using AI wrong. GitHub Copilot autocompletes your code. ChatGPT writes functions you copy-paste. Claude suggests implementations you review line by line.