|
|
|
|
|
|
by _pdp_
86 days ago
|
|
|
So this is a wrapper on top of a wrapper on top of Claude Code (which is a wrapper) on top of the API. Considering that Open Claw requires 2GB of RAM and Claude Code is by no means a "lightweight" CLI either, I would argue that the compounding overhead here is hard to justify when you could just hit the API directly. Each layer adds its own memory footprint, failure modes, and debugging surface area and at some point, the convenience of abstraction is outweighed by the cost of running what is essentially a Matryoshka doll of Node processes just to send a prompt and get a completion back. Just a thought. |
|
|
Relay connects to OpenClaw. OpenClaw connects to whatever model provider you choose (Claude, GPT-4, Llama, custom endpoint, whatever).
So the stack is: Your local files → Relay → OpenClaw gateway → Your chosen model.
That said, your point about abstraction overhead still stands. Each layer adds cost. We think the tradeoff is worth it for teams that need always-on agents + local file access + approval workflows. But if you just want to hit an API directly, you're right — this isn't for you.