See It In Action
A real conversation with a MeClaw agent — running entirely inside PostgreSQL.
Why MeClaw?
Pure PostgreSQL
No runtime, no sidecar, no message queue. The database is the agent runtime. Extensions do the heavy lifting.
Event-Driven
Trigger chains fire on every INSERT. Zero polling in the hot path. Messages flow through the system like electrical signals.
Graph Routing
Apache AGE powers the routing layer. Agent topology defined in Cypher. Change behavior by editing the graph — no code deploy.
Hive & Bee Architecture
Bees are pure functions — one input, one output, no loops. The Hive is the container. Isolation by design.
Built-in Tools
SQL read/write and Python execution out of the box. The LLM decides when to use tools. Results flow back through the event chain.
ACID Guarantees
Every event is an append-only log entry. ACID transactions. WAL for recovery. Point-in-time restore. Your agent state is as safe as your data.
How It Works
Message arrives
A user sends a message via Telegram, web chat, or direct SQL. It lands as an INSERT into the messages table.
Trigger chain fires
A PostgreSQL trigger instantly wakes the router_bee. No polling. No sleeping. Pure event-driven reaction.
Graph routes the message
Apache AGE reads the agent graph in Cypher and decides which bees to activate — context, LLM, tools — in what order.
LLM thinks, tools execute
The llm_bee calls any provider (local vLLM, Claude, GPT). If tools are needed, the tool_bee runs SQL or Python — right inside the DB.
Response delivered
The sender_bee delivers the answer back to the user. The entire round-trip: <2 seconds. Everything logged, everything ACID.
Architecture
One PostgreSQL container. Everything inside. Hover to explore.
100% Vibe-Coded
This entire project — every SQL function, every trigger chain, every line of Python, the README, and this website — was built through conversation.
The human (Marcus Meyer) designed the architecture and made decisions. The code was written by Claude Opus 4.6 via OpenClaw.
No line was typed by hand.