The End of the Middleman

For as long as AI coding tools have existed, there has been a translation layer: the developer. A PM describes what they need. A developer translates it into a prompt, waits for output, interprets the result, relays it back. Every handoff adds latency and miscommunication. Half of all developers lose more than ten hours a week to this — fragmented tooling, context-switching, playing translator for work that shouldn’t require them.

Peter Steinberger saw it clearly. In November 2025 the Austrian developer — who built PSPDFKit into a tool used by Apple and Dropbox before selling his stake — open-sourced a side project called Clawdbot. It let anyone text an AI agent on WhatsApp and have it do things: clear an inbox, book a restaurant, control a smart home. No IDE. No terminal. Just a message. Within weeks the project was gaining thousands of GitHub stars a day. Steinberger had proved what the industry was about to absorb: the demand for AI without a developer in the loop is enormous.

Claude Channels starts from the same insight. By putting Claude in Discord and Telegram — tools non-technical teammates already use — anyone on a team can describe what they need and get results directly. A PM checks the status of a feature flag. A designer requests a copy change. An ops lead pulls a data summary. No ticket filed, no developer interrupted.

This doesn’t diminish the developer’s role — it refocuses it. Developers concentrate on architecture, debugging, and system design. The rest of the team gains autonomy they’ve never had. The question is no longer whether the middleman role will shrink, but how fast.