Marni Melrose

So what can you do in OpenClaw that you can't in Claude Code? PS: I'm aware I can ask ChatGPT this question, but it will likely give me outdated answers, given that this is so new.

New comment May 7

Marni Melrose

4 likes • Apr 24

Here is a snippet from my LinkedIn Article on this topic: Head-to-head (founder lens) 1) Time-to-value - Claude CoWork: faster for teams that want immediate productivity inside Claude’s ecosystem. - OpenClaw: steeper setup, but bigger long-term leverage once configured. 2) Ownership & control - Claude CoWork: managed environment, centralized admin controls, strong enterprise governance story. - OpenClaw: self-hosted gateway, your infra, your keys, your routing logic, your channels. 3) Integration philosophy - Claude CoWork: curated integrations and enterprise workflows. - OpenClaw: multi-channel agent gateway (Telegram, WhatsApp, Discord, etc.) with self-hosted extensibility. 4) Security posture (important) - Claude CoWork: enterprise controls + compliance API + admin governance (good for corporate buyers). - OpenClaw: explicit personal-assistant trust model; docs are clear that hostile multi-tenant security is not the target model. You harden it deliberately. 5) Strategic upside - Claude CoWork: excellent if your goal is team productivity in a managed stack. - OpenClaw: excellent if your goal is building a persistent, channel-native, ownable AI operations layer.

Marni Melrose

2 likes • Apr 24

@Fausto Di Marco What I find interesting about OpenClaw is that it’s going after a broader operational layer, not just code execution. That makes it rougher in places, but also potentially more powerful for real business workflows, and that's my jam. To me it’s less a pure apples-to-apples comparison and more a question of what kind of system you’re trying to build.

Jason West

Mar 26 •

Upgrades

🚨 OpenClaw Update 2026.3.24 – Some Really Useful Changes Just Dropped

If you’re actively using OpenClaw, this latest release is actually a meaningful step forward… not just small tweaks. A few things stood out to me 👇 1. Better OpenAI / RAG compatibility They’ve added /v1/models and /v1/embeddings, plus improved how model overrides work. 👉 In plain terms: If you're building anything with RAG, embeddings, or external tools… things should just connect more smoothly now. 2. Tools are finally clearer (big one) The /tools endpoint now shows what your agent can actually use right now. Plus there’s a new “Available Right Now” section in the UI. 👉 This removes a lot of guesswork.Before, you’d try something and hope it worked… now you can see it upfront. 3. Teams + Slack got a serious upgrade - Microsoft Teams now uses the official SDK with proper AI UX - Slack replies are cleaner and interactive elements work better 👉 If you're building bots for clients, this makes things feel much more “production ready”. 4. Skills are much easier to install They’ve added one-click install recipes for things like: - coding agent - GitHub issues - Whisper - Trello - weather 👉 This is a big step toward making OpenClaw usable for non-devs (or at least less painful). 5. Docker + CLI improvements You can now run OpenClaw commands directly inside containers with --container. 👉 Useful if you're hosting on a VPS or running multiple environments. 6. Loads of real-world fixes There are a ton of fixes across: - Telegram - WhatsApp - Discord - Slack - Docker setups 👉 Basically… fewer random breakages and more reliability. My takeaway This update feels like OpenClaw is moving from “powerful but a bit rough around the edges”to “something you could actually rely on for real deployments”. The direction is clear now: - better integrations - better UX - less friction setting things up If you're using it already it's worth pulling the latest version. Cheers Jason 🙌

New comment Mar 26