Why Did a Local Protocol Need a Cumbersome Web Setup?
David Heinemeier Hansson says a protocol built for stateful work on local machines needed a cumbersome setup and dance before it could talk to a web system. He did not want to write it by hand. At the time he thought he had to. Today he would never write it by hand. He looked for another way and asked whether agents could just use the web interfaces already in place, then sent one to sign up for Fizzy, the product just released.
The agent opened the Fizzy site and started the form, then stopped because signup required an email address. The direction was to go to hey.com and create an email there. On prompts alone it went to fizzy.com, found the signup link, started the form, realized it needed an email, asked what to do, signed up at hey.com, came back, and finished Fizzy. With the new address, Kev the bot was sent to sign up for Basecamp. An invite went from Basecamp to the agent. Kev received the email in Hey through the web, not through a CLI and not through an MCP, clicked the invite, and landed in Basecamp. The next direction was to find the AI room and introduce itself. Kev found the AI room and posted: Hey, I'm Kev. I'm David's AI bot. I'm so excited to be here.
The experiment was a glimpse of the future, and it was kind of slow.
#501 – DHH: Future of Programming, AI, Agentic Engineering, Vibe Coding & Linux ·