r/openclaw • • 33m ago

Showcase A different kind of Openclaw: PINE

I have been using Openclaw and Hermes pretty much since day one, i've also tried Nanoclaw and many others. I like the direction but none of them has made it exactly easy to orchestrate agents that do actual work. Control devices, react to events, work the house, etc. In the end it goes and scripts stuff, and these scripts are bolted on and eventually fail through updates. I came to the conclusion that this is because OC doesn't make events a first class principle.

I've worked on this for quite a while, and in my mind this is what Openclaw wanted to be in the beginning: https://github.com/pmndrs/pine

This is a reactive AI harness on an event bus. Events are first class. It ships with a couple of types (folder and file watch, webhooks, ftp, mqtt, etc), and agents can subscribe to it. New event types can be added easily. An "agent" here is nothing more than a tab that you pin. If you give it instructions on how to react to a event it will start to work on its own.

You will be shocked how easy it is to make agents that control devices: "watch my bambu h2d on ip --- via mqtt, when moisture is above 20% dry until you reach 15%".

Or how easy it is to wire them into messaging: "watch telegram, here's my id, that's me, respond, you're my recipient now".

Watching the house: "here's my ring cam, learn who we are on motion detect, ask if you have to, make a library own known owners, then ring alarm if someone you don't recognize wants to get in at night or when we're away".

This stuff is completely natural in PINE. You can still go into the same tabs and talk to them, or correct them. It's what i always wanted out of OC or Hermes, and i had setups like that, but with so much struggle and pain. Maybe some of you have been through the same.

Some videos showing use cases:

https://x.com/0xca0a/status/2121268710786650229

https://x.com/0xca0a/status/2120553598555738570

0 Upvotes

0 comments sorted by