In this post I want to share some thoughts on how emergence made OpenClaw so successful and what that means for Grasshopper and Raven.
OpenClaw is the latest project creating significant buzz in the AI scene. For those who don’t know: OpenClaw is an AI Agent that lives on your computer and can do almost anything there (sounds like a great idea, right?). But here’s why people are loving it:
LLMs have been around for a while now - and they can be useful for some isolated tasks such as writing an email, but the promised ‘AI Asisstant for everything’ has not yet materialized to the extent we were hoping for. The dramatic rise in popularity of OpenClaw suggests that the project actually brought us a significant step closer to [whatever we were expecting].
Emergence
The reason why OpenClaw is so successful is that its Agent benefits from emergence. An LLM that can write emails is not that useful by itself. An LLM that can add events to your calendar is not that useful by itself either. But when you combine those simple skills, the Assistant can ‘schedule meetings with others’. Without adding, but from combining, you get a skill that is actually quite useful.
On Wikipedia ‘emergence’ is described like this:
emergence occurs when a complex entity has properties or behaviors that its parts do not have on their own, and emerge only when they interact in a wider whole.
Let’s consider how Grasshopper benefits from emergence and what that means for AI agents such as Raven. Grasshopper is well known and loved for its flexibility and customizability (you are probably aware of that that if you’re reading this forum). People use Grasshopper because it allows them to modify and tweak their workflows in ways that other CAD software doesn’t.
With around a thousand (!) plugins published on food4rhino, Grasshopper has been extended with capabilities that other platforms can only dream about. This is why Autodesk added Rhino.Inside for Revit. I mean, think about it: Autodesk allows you to install their competitor as a Plugin…
An AI agent that can model simple geometries is great. But what’s better is an agent that can do real-time physics simulations (Kangaroo), environmental analysis (Ladybug), load terrain data (Elk) or perform finite element analysis (FEA). And if you’re missing a feature, you can just add it yourself.
That’s why built Raven in Grasshopper - on its own Raven wouldn’t amount to much. But by integrating with the Grasshopper ecosystem early, Raven became the most versatile CAD Assistant out there right now.
I’m curious to hear what your thoughts are on this - where do you think we’re headed with CAD agents? Have you had success with automating workflows in CAD yet?
Max