Understand OpenClaw by Building One - 4: Beyond the CLI

1. Every Agent Starts as a Loop 2. Gear up Your Agent 3. Pack the Conversation And Carry On 4. Beyond the CLI 5. Many of Them 6. Agents are Running, Your are Sleeping 7. More Context! More Context! Beyond the CLI Your agent works great in the terminal. But what if you want to talk to it from Telegram? Or your phone? Or another program? Or even multiple of them. Event-Driven Architecture To make the agent more scalable, we introduce event-driven architecture before adding more feature. The pattern is pub/sub, and you already know it. An event bus sits at the center. Messages come in as events, workers process them, responses go out as events. @dataclass class InboundEvent : session_id : str content : str source : EventSource @dataclass class OutboundEvent : session_id : str content : str error : str | None = None class EventBus ( Worker ): def subscribe ( self , event_class , handler ): """ Subscribe a handler to an event class. """ async def publish ( self , event : Event ) -> None : "