Right. I'm on it.

Probably not the typical OpenClaw user. I’ve had that thought myself.

But I can imagine that medium-sized companies will want to use AI as a backend in the future, without wanting to be dependent on Antropic.

After all, there are already quite a few companies using OpenClaw.

A self-hosted OpenClaw instance (or other solutions in the future) with Relay would be a good alternative to Claude Cowork.

You're right, that part is a bit confusing. I'll have to fix it.

I'm not entirely sure what Cowork means by “sandboxed VM” right now. Relay simply has access to the folder you've defined for the project.

What makes you think this is AI slop?

The first impression I get looking at the README and the website doesn't suggest much effort went into it.

Who is the troll here? I asked a genuine question and tried to explain why I think this way, and now you're all toxic. Can't you take feedback? If not, then why did you post this project here?

Actually, Relay doesn't sit on top of Claude Code.

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.