Key Takeaways

  • Peter Steinberger built OpenClaw to push models beyond passive chat and give them direct execution tools to buy goods, install local software, and manage desktop workflows.
  • Steinberger resolved display glitches on a custom ESP hardware device by gluing a webcam to the screen and letting Codex debug the display driver overnight.
  • The upcoming software battle pits user-owned autonomous agents against corporate platforms attempting to trap consumers inside proprietary bots.
  • Developers will soon treat the operating system as prompt-editable software, turning fixed system rules into malleable code.

Stop Summarizing Emails and Give the Model Root

Most software teams build AI features like polite assistants waiting for a prompt. They build sidebars that summarize unread emails or draft chat replies. Steinberger thinks that approach misses the point entirely. Models should control the machine directly.

“I think I just showed people a different way how to use AI and so many were stuck in this world,” Steinberger said. “Oh, it can summarize my email. No, it can install stuff on your computer or buy things for you or do whatever you want that you can do in your computer if you just only give it the right tools.”

True autonomy requires letting models run loops, execute scripts, and take initiative. When Steinberger ran into display issues on a custom ESP microcontroller, he did not spend the night reading technical manuals. Instead, he glued a physical webcam to the display, pointed Codex at the setup, and let it run unattended tests all night until the driver worked.

That loop burns tokens fast. Steinberger admits it openly: “Some of it was token burning, but some of it was genuinely cool and surprised people.” Burning compute to fix hardware problems on your desk beats spending twelve hours writing manual firmware patches.

The Agent Wars: Your Bot Versus Their Bot

Every major tech company wants to stick an official assistant between you and their service. Airlines want you inside their booking bot. Marketplaces want you inside their shopping assistant. Steinberger sees this as a conflict between user control and platform capture.

“There's so many companies that want to own the experience and I don't want to talk to your agent,” Steinberger argued. “I want my agent to be able to use your system in the way it thinks it's best.”

This shift creates the agent wars. In this setup, your personal agent negotiates terms, scrapes uncooperative interfaces, and bypasses artificial checkout friction. The platform wants to control how you buy; your agent wants the fastest, cheapest path. Software will no longer be designed for human eyeballs looking at buttons. It will be an adversarial surface between user-side autonomy and platform restrictions.

The Operating System as a Prompt

Once you get used to modifying web apps and scripts by typing plain English instructions, rigid operating systems feel broken. Steinberger views the desktop OS as the final barrier standing between developers and complete control.

“I kind of get annoyed if I can't change software as a prompt,” Steinberger said. “Got so used to having all the tools myself that now I'm kind of annoyed at the operating system, because it feels like the last frontier.”

Instead of accepting fixed UI paradigms or kernel boundaries, future builders will treat the entire system stack as prompt-editable code. If an application lacks an export button, your agent inspects memory or injects an override. If an OS refuses a workflow, the agent rewires the system call.

What to Do With This

Audit your product roadmap this week. If you are building a custom chat agent that forces users into a closed support flow, stop. Expose raw, authenticated API hooks and clean computer-use endpoints so your customers' personal agents can interact with your service directly without getting blocked.