1) accessibility to non-technical folks. For the first time, they are having the Claude Code experience that we've had as software engineers for some time now
2) shared, community token context. Many end users are contributing to one agent's context together. This has emergent properties
Next, consider how you might deploy isolated Claude Code instances for these specific task areas, and manage/scale that - hooks, permissions, skills, commands, context, and the like - and wire them up to some non-terminal i/o so you can communicate with them more easily. This is the agent shape.
Now, give these agents access to long term memory, some notion of a personality/guiding principles, and some agency to find new skills and even self-improve. You could leave this last part out and still have something valuable.
That’s Openclaw in a nutshell. Yes you could just plug Discord into Claude Code, add a cron job for analyzing memory, a soul.md, update some system prompts, add some shell scripts to manage a bunch of these, and you’d be on the same journey that led Peter to Openclaw.
But a message bot + Claude Code/Codex would be the better version
Non-technical people haven't even heard of OpenClaw or Github, let alone know how to use and deploy them. Non-technical people don't even know what OS their Samsung or iPhone is called.
If you can find something on Github and deploy it on your system, you're part of the technical crowd.
(Not that I endorse that. I find peoope doing such wildly irresponsible.)