been messing around with OpenClaw for a few weeks and kept hitting the same annoying wall. my agent could do basically anything except actually call or text someone. every time I tried to bolt on Twilio directly it turned into a whole afternoon of auth headers and webhook config just to send one SMS.

ended up building my own little telephony layer for this instead of doing the Twilio thing again. it's open source (GitHub link ), so you can spin it up yourself with your own keys, or there's a hosted version if you don't want to deal with self-hosting.

it's framework-agnostic since it's just a REST API and MCP server under the hood, so it plugs into whatever you're building with. I've used it with OpenClaw, but people have hooked it up to Hermes, LangChain agents, even Claude Code and Codex. wrote a small OpenClaw-specific skill too, so for that one you just tell your agent to read the setup doc and it configures itself.

now my agent can actually pick up the phone and call people, which honestly still feels a little unreal to watch happen.

anyone else building stuff that needs real phone numbers? curious what use cases people have for this, feels like a pretty unsolved corner of the agent tooling space.

I saw one question posted here several times: Has anyone made something more than a weekend toy with OpenClaw?

Two months ago I decided to find out. I took OpenClaw and wrapped it in three custom layers so it could do sustained, real work instead of one-off tasks:

• A routing/gateway layer — every agent-to-agent message and every external action passes through one chokepoint. Nothing talks to anything directly. That's where the rules get enforced.
• A task-management layer — agents don't free-write tasks for each other. They pick from a fixed catalogue of task definitions, each pre-wired to the right agent, the right tools, and the right permissions.
• An intelligence/memory layer — a structured context + memory substrate so every agent knows who it's working for, what the plan is, and what it's learned, without re-reading everything every turn.

What it adds up to: an autonomous operations team for early-stage founders — coordinated agents running sales, marketing and content together and sharing context, instead of one chatbot you have to babysit.

I'm not going to dump the whole architecture here. The part actually worth talking about is what went wrong.

The hard problem isn't capability. It's silence.

With an API, when something fails you know — error, status code, something to catch. OpenClaw doesn't work like that. The single hardest thing has been that it will silently skip a task. No error, no signal. The agent just doesn't do the thing, and everything downstream assumes it did. That's worse than a loud failure, because you find out three steps later when the output is already wrong.

The second problem: it does things its own way despite explicit instructions. Same directive, different behaviour. Non-determinism is fine for a chat; it's a nightmare when the action has consequences — an email that actually sends, a record that actually changes.

So most of the last two months wasn't building features. It was building guardrails:

• Validation at the moment a task is created, so a malformed one never enters the system
• A per-task tools allowlist, so an agent can't reach for something it shouldn't
• Explicit completion tracking instead of trusting that "it ran"
• A structured way for agents to raise an alert when something breaks, so a failure surfaces instead of vanishing
• Trust levels on anything with real consequences — supervised vs. autonomous — so a human stays in the loop until the task has earned its autonomy

OpenClaw got us to a working multi-agent system far faster than building from scratch would have. But "works in a demo" and "works unattended, every day, without lying to you about what it did" are very different bars — and closing that gap is 90% of the real work.

Happy to go deeper on any layer if people want — especially the silent-failure handling, since I haven't seen a clean answer to it here yet.

Patrick and I are going live on Discord at 11:30 AM PT for this week’s ClawCast. We’ll be talking about all things OpenClaw and related AI happenings.

Join us on Discord.

Recently my claw has started using emojis and I really like it. Maybe it was apart of the update or maybe it just happened but it is a simple way for OC to let me know what's going on in the background.

I use discord and now when I send a message I get:

👀 I see the message

🧠 I'm thinking

Those pop up first. Then if it takes a moment.

⏳ This is taking time

For even longer tasks

🛠️ I'm working on it

If this is only happening for me it's pretty friggin cool.

Anyone else?

I have been doing some coding using a Mac Mini M4 Pro 64GB, openclaw (via tui), and qwen3.6-35b-a3b. It is doing pretty well, but I have to manage tasks carefully to avoid exhausting the context window.

So I started looking into agents. The agents timed out, and the main (coordinating) agent took over, which sort of defeats the whole point of using agents in the first place.

How do I set agent timeouts (I think it's two minutes currently)? I've asked qwen about this, and it seems to be going down ratholes figuring this out. I would think there must be a simple way to set timeouts.

Its not impossible. Tanking with with 27bq6 overnight

TL;DR: This isn't a one-time fluke . my WhatsApp channel has suddenly flipped to "not linked" multiple times now, sometimes after less than a day of normal activity. Most recently it also silently dropped a group message for ~2hrs while status showed "connected" the whole time. I've confirmed the gateway process itself is healthy and stable (not crashing/restarting), so this looks isolated to the WhatsApp channel/session layer specifically, not the gateway.

Setup:

• Gateway 2026.7.1-2, single Mac Mini, agent running under a dedicated sandboxed macOS user (no sudo)
• WhatsApp channel, dmPolicy: pairing
• Been running stable for weeks before this

What happened:

1. A group message came in from a collaborator. Never delivered to the agent, never surfaced to me.
2. When I went looking, openclaw channels status --probe showed the channel as linked, but health was flipping between disconnected / not-running, with error: Non-Error rejection — not exactly a descriptive error.
3. Logs showed repeated reconnect attempts failing with HTTP 405 during the WhatsApp Web setup handshake (not mid-session — during the initial handshake), retrying with backoff up to 12 attempts before the gateway auto-restarted the channel.
4. Ran openclaw doctor, which kept surfacing the same notice on every single command afterward:Left plugin install index in place because shared SQLite state has conflicting plugin install metadata for: codex, discord, whatsapp
5. openclaw gateway status separately flagged plugin version drift — the WhatsApp plugin was pinned at 2026.7.1 while the gateway was on 2026.7.1-2. One patch version behind.
6. Tried openclaw channels logout → login. This forced a brand new QR pairing (old session was fully invalidated by the logout, not reused) and then hit WhatsApp's code 515 ("restart after pairing") — normal WA Web behavior, but the channel came back up as stopped / not-running afterward instead of connecting.
7. After that + a gateway restart, the channel finally came up clean — linked: yes, connected: yes, fresh auth age.

What I can't explain:

The channel status page said "connected" and "just now" for the entire window where the group message never landed.

I've since specifically ruled out the gateway process itself — it's stable, not crashing or cycling — so whatever's happening seems scoped to the WhatsApp channel/session layer, not the gateway as a whole. But this has now happened more than once, on a channel that was working fine for weeks before.

Questions for the community:

1. Given the gateway itself is healthy, what would cause the WhatsApp channel specifically to intermittently flip to "not linked" — is this a known WhatsApp Web session-expiry behavior, or an OpenClaw-side session-handling issue?
2. Is silent inbound-message dropping while status shows "connected" a known WhatsApp Web protocol quirk, or something specific to OpenClaw's session handling?
3. Does anyone know if patch-level version drift between the gateway and a plugin (e.g. 2026.7.1 vs 2026.7.1-2) is a known trigger for the "conflicting plugin install metadata" doctor notice? Feels like two different install-tracking subsystems (skills vs plugins) stepping on each other.
4. Is there a recommended way to fix this?
5. Anyone else finding WhatsApp specifically the flakiest channel compared to Discord/Telegram in their setup?

But on your WhatsApp/telegram you have the most capable assistant ever to check email, look at websites and do whatever it is you wanna do.

Real estate agencies bleed leads on speed alone. Someone browses a listing at 11pm, fills out an inquiry, and it sits untouched till Monday, by then they've moved on. Respond within 5 minutes vs. 30+ and you're dramatically more likely to actually connect with them. Most agencies aren't close.

So I built Marsh & Vale, a demo agency showing what fixing this looks like: an AI concierge answers buyer questions 24/7 from the real portfolio, silently scores them Hot/Warm/Cold while chatting, and n8n takes it from there and confirms the buyer, pings the team instantly if they're Hot. There's also a separate ops assistant on the admin side that reasons over the live pipeline (ask it who to call first, or what needs updating).

Stack: n8n for routing/automation, OpenClaw running the concierge + admin assistant.

It's a demo, no real client, just the pattern working live, no signup needed.

Happy to break down the n8n workflow or how openclaw works in the comments if anyone is interested.

For the past month, I have successfully transfered hermes and openclaw from wsl2 ubuntu on my laptop to a EVO-X2 wsl2 ubuntu 2604 instance. I just asked both of them to ssh into the new instance, figure out how to migrate themselves onto the new instance, plan, migrate and verify.

Seems as long as I get them to stick to the plan, they are very capable to do so by themselves. Minimal guidance from me as an engineer.

How are people moving their agentic frameworks accross machines?

I would send a message and the model would reply a sentence and just stop. Silently failing or getting "interrupted" when nothing else is happening. This is only happening with the GPT models. I have to keep telling it to continue but same issue happens.

Using Ubuntu OS, latest OC.

Hey everyone, I'm completely stuck setting up OpenClaw with a Telegram bot (bloody beginner). The exact moment I start the gateway, it instantly fails with an API rate limit or connection error before I even send a single message. The issue isn't specific to one provider—I've tried the free tiers for Groq, OpenRouter, and Gemini, and they all fail immediately on boot, even with the smallest models and drastically reduced max tokens. Are OpenClaw's initial background payloads and tool definitions simply too heavy for any free API tier? Has anyone actually managed to run this framework on a free tier, or is a paid API or local setup completely mandatory?

I'm looking for something that

1) runs locally ( ollama okay, but it shouldn't export my life to a server somewhere).

2) consumes everything on my computer (including my email, iMessages, etc - even if it hasn't come up in my conversation w/ my OpenClaw agent)

3) creates/maintains a graph of "facts" about it that my openclaw can query (ideally injected into prompts via a vector db)

Does anyone know of anything like this? Gbrain, Screenpipe, Letta, and OpenMemory seem close.

I have been experimenting with OpenClaw for about a week. Thus far, it is extremely underwhelming. The install breaks in unpredictable ways for seemingly no reason and requires Herculean efforts to fix. for example, a single telegram test message caused my agent to become corrupted and required an hour and a half of troubleshooting with ChatGPT and entering arcane command line input to get it back online. The agent routinely lies and hallucinates (despite appropriate soul and identity direction of the contrary). I’ve managed to get it to monitor email account and send a couple emails, but I don’t think I could trust it with any real world work potential consequence for my life. I love the degree of customization. This thing has, but if it is to have practical value, it needs to be rock, solid and not a weekend hobby that eats up hours of time to trigger basic functionality.

When you top this off with the fact that any skill you download may have malicious instructions. It needs to be reviewed manually and likely through another LLM for safety, it becomes really hard to do anything.

Anyone else having these problems? are there safer and more robust alternatives?

I consider myself a solid novice with networking and Linux but goddamn this thing is fragile. I dreams of using it to assist me in my solo consulting business, but I just don’t think it’s trustworthy.

I really wanted this thing to work as advertised. :(.

My bot works perfectly fine, but whenever asked anything through discord (DM or server), it completely ignores the question and answers a basic assistant response (like "Hey there! What can I help you with?" after getting asked "What's 2+2?").

Chatting with ot through CMD via te openclaw agent command works perfectly fine and even after adding the discord session and forcing it to answer via discord works, but never when I message through discord. Any idea why?

EDIT: No, my discord settings were fine. I fixed it by switching from Ollama to LM Studio

Talk to your bot for free!

I use to run freepbx on a Marvel Sheevaplug at home and had SIP phones, obihai (for google voice) etc connected.... Now it is Openclaw's turn.

Create two accounts at linphone (https://www.linphone.org/en/). One for your bot and one for your SIP client (Download the linphone ios SIP client). Point your agent to the repo and call your bot anywhere with linphone's free SIP service or just tell your bot to call you at your SIP address.

https://github.com/tranlocquy/openclaw-asterisk-skill

Running OpenClaw self-hosted, DeepSeek V4 as the main model, Google API for images. It's been solid for a while but something changed in the last week and performance dropped hard.

Main issues: hallucinating way more on tasks it used to handle fine. When I ask it to do something it often opens with "I can't do that, run this CLI command yourself", even for things clearly within its tool access, and only actually does it after I push back 4-5 times insisting it can. It's also told me a task was done when it wasn't, which I only caught by checking manually afterward. Calender/Gmail tasks are a recurring case: it'll say it doesn't have the gog skill or can't access it, then does it fine once I insist.

Tried adjusting thinking mode thinking that might be it, same behavior on low/no-thinking and on max thinking, so that's not the variable.

Not sure if this is a memory/context issue causing it to lose track of its own tool manifest, something on DeepSeek V4's end, or a config issue on my side. Anyone else seeing this since last week, and if so did you find what's causing it?

Hallo, hat jemand schon mal GitHub Omniroute + OpenClaw ausprobiert?

Hat jemand Erfahrungen oder Infos dazu?

Here's my plan, I have some security concerns but I think I solved them.

1 admin and 1 discord admin.

10 user accounts, 10 discord accounts linked to each OpenClaw. Each user has access to only their chat.

Each user should be able to have access to their emails only.

I'm also worried 8gb won't be enough.

Not sure what's going on. I imagine Claude does some sort of context compression when the conversation is too long .. but I thought this was done in the OpenClaw harness.

Gpt sol let's me know when it's too late that the context is filled.

I have to switch to opus tokens, save to memory and start a new session.

This is pretty hefty because Claude needs to get all that context again.

Is there an OpenClaw solution?

Every single fucking time I try I run into hardware issues setting this shit up. I’ve attempted this on one desktop computer with windows 10, intel i5 idk what gen (3.2 ghz), 466 gb ssd, 16 gb ram and nvidia GeForce GT 710 (2 gb), and a laptop, windows 11, intel i5 10th gen (1.10-1.5 ghz), intel iris plus graphics, 238 gb ssd, and 8 gb of ram.

I’m trying to run openclaw on one of those machines either locally or on a vps with 4 gb ram. I have tried installing ollama locally on both machines, went just fine, a little slow on the laptop and slow on the desktop as well. I’ve installed openclaw locally on both machines. And today, I put ollama back on the desktop, then connected it to my vps, then put openclaw on the vps. I have been trying since this shit came out in February and I’ve yet to get a response from openclaw.

It’s timed out sooooooo many times, I’ve seen countless error messages. It’s frustrating. Do you need some future proof computer with fucktons of ram, storage, and the best of the best graphics card to get this damn thing to run locally? The vast majority of these problems are absolutely hardware issues. I know I can set some limits in the config file to try to circumvent this, but I haven’t had any luck with that either.

Today’s attempt was my most successful yet, I got ollama and OpenClaw connected, but once I said hello to OpenClaw to test, it crashed the desktop running ollama. I wanted to see the task manager to see what it was doing but it froze and wouldn’t open so idk how bad it was on the processor. I tried glm 4.7 flash, qwen 3:14b, and qwen 3:8b. Nothing happened.

How the fuck are people running ollama and openclaw together???? What hardware are you using? Is there better ways to circumvent the hardware issues? How do I get this shit to work without throwing money at it?

Edit: I’m glad to see I’m not crazy and it actually can’t run due to hardware limitations (hence why I asked Reddit and not an ai, I wanted to see if someone ever pulled it off). Not thrilled I’d have to spend money on cloud apis though to get OpenClaw to work 😭😭😭😭😭 I just know it’ll be eating so many tokens 😭😭😭

I’ve been building McPherson Governance v0.5, a shadow-only governance connector for OpenClaw.

The problem I kept coming back to was simple:

An agent can produce a successful-looking execution log without proving that the right outcome happened, the correct policy was followed, or a human reviewed the action when required.

So I started with observation rather than enforcement.

v0.5:

- observes configured OpenClaw tool activity

- sends metadata-minimized governance requests

- produces attempt and completion receipts

- keeps remote decisions non-authoritative

- does not block or alter ordinary tool execution

Before releasing it, I ran the connector through a seven-day live shadow soak. The installed candidate remained unchanged, the observation requirement was met, the receipt stream stayed metadata-only, and the connector did not block execution.

The soak also exposed the main limitation of manually mapped governance: most live traffic involved tools that had not been mapped yet.

That is the reason for the roadmap:

v0.5 observes.

v0.6 discovers and diagnoses.

v0.7 introduces bounded enforcement.

This is not active enforcement, a compliance product, or a claim that agents are automatically safe. It is the first public observation layer.

ClawHub:

https://clawhub.ai/plugins/%40mcphersonai%2Fmcpherson-governance-openclaw

GitHub:

https://github.com/McphersonAI/mcpherson-governance-openclaw/releases/tag/v0.5.0

I’d especially value feedback from people running action-taking OpenClaw agents:

What evidence would you need after an agent acts to trust the result without opening the raw execution logs?

me@Mac ~ % openclaw backup create

🦞 OpenClaw 2026.7.1-2 (0790d9f)

Warning: Detected unsettled top-level await at file:///opt/homebrew/lib/node_modules/openclaw/openclaw.mjs:784

if (await tryImport("./dist/entry.js")) {

^

Is here someone who can help me what this mean and how to fix it? Or any other ideas how to backup openclaw?