HNHacker News
TopNewBestAskShowJobs

chrislxy

6 karma · joined January 21, 2026

submissionscomments
chrislxy··on Show HN: I replaced my X analytics dashboard for a daily "what to do next" brief
Thank you! I works for every account.
chrislxy··on Show HN: I built a lead list tool to find businesses you can sell to
Thanks, Beannation! Is there anything I can improve? What would you like to see, or what do you need to use sensecollect regularly?
chrislxy··on Show HN: Relay – The open-source Claude Cowork for OpenClaw
Right. I'm on it.
chrislxy··on Show HN: Relay – The open-source Claude Cowork for OpenClaw
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.

chrislxy··on Show HN: Relay – The open-source Claude Cowork for OpenClaw
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.

chrislxy··on Show HN: Relay – The open-source Claude Cowork for OpenClaw
What makes you think this is AI slop?
chrislxy··on Show HN: Relay – The open-source Claude Cowork for OpenClaw
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.