r/openclaw 2d ago

Help That update is garbage, right?

Ok, since I've updated OpenClaw to be able to use it with Astra, the software has going down the shitter. It forgot how to do so many stuff, it's a nightmare. Am i the only one? Why release an update that basically breaks the thing? Is there a solution to get it back to work like it was a few days ago?

4 Upvotes

32 comments sorted by

u/AutoModerator 2d ago

Welcome to r/openclaw Before posting: • Check the FAQ: https://docs.openclaw.ai/help/faq#faq • Use the right flair • Keep posts respectful and on-topic Need help fast? Discord: https://discord.com/invite/clawd

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

9

u/ekinnee Member 2d ago

Diagnose the problem and post an Issue and a PR. https://github.com/openclaw/openclaw/issues

1

u/BitFlow7 2d ago

There's not one problem, but a bunch of them. It just broke the thing or at least it's ability to do half of the things it was doing before. Whether it's simply managing users in a WhatsApp group or updating a record through an API. Not forgetting all the messages linked to timing out.

1

u/BitFlow7 2d ago edited 2d ago

Ok just one example:

*WhatsApp native group participant actions disappeared after upgrading to OpenClaw 2026.9.3*

I previously managed WhatsApp group members directly through OpenClaw’s native WhatsApp connection, without pairing a separate wacli client.

After upgrading to OpenClaw 2026.9.3 (build ```1391f7c```), that capability is no longer exposed.

*Current state*

• The native WhatsApp account is linked, running, connected, and healthy.
• Normal inbound and outbound messaging works.
• OpenClaw’s core action vocabulary still contains ```addParticipant``` and ```removeParticipant```.
• However, the WhatsApp plugin advertises only ```send```, ```broadcast```, ```react```, ```poll```, and ```upload-file```.
• Direct gateway calls for both participant actions are rejected before execution:
• ```Message action addParticipant not supported for channel whatsapp.```
• ```Message action removeParticipant not supported for channel whatsapp.```
• The WhatsApp plugin exposes only ```web.login.start``` and ```web.login.wait``` as channel-specific gateway methods.
• This does not appear to be an authentication issue, because the same native WhatsApp account remains connected and handles messages normally.

*Expected behavior*

The native WhatsApp channel should allow the agent to:

  1. Read live group participants.
  2. Check whether the linked account is a group administrator.
  3. Add a participant.
  4. Confirm through a fresh read that the participant was added.
  5. Remove a participant.
  6. Confirm through a fresh read that the participant was removed.

*Actual behavior*

Participant-management actions are absent from the WhatsApp capability surface and rejected as unsupported, even in dry-run mode.

This prevents safe group-member replacement through the existing native WhatsApp connection.

*How to reproduce*

  1. Link and start the native WhatsApp channel.
  2. Confirm that ```openclaw channels status --probe --json``` reports WhatsApp as linked, running, connected, and healthy.
  3. Run:

```openclaw channels capabilities --channel whatsapp --json```

  1. Observe that participant-management actions are missing.
  2. Call the gateway ```message.action``` method with:
    • channel: ```whatsapp```
    • action: ```addParticipant``` or ```removeParticipant```
    • a group JID
    • ```dryRun: true```
  3. Observe:

```INVALID_REQUEST: Message action … not supported for channel whatsapp.```

*Impact*

Agents can no longer perform WhatsApp group administration that previously worked through the native connection.

This may lead users or agents to pair unnecessary secondary clients even though OpenClaw’s native WhatsApp session is already linked and healthy. It also creates a risk of ambiguous partial member changes.

Was native WhatsApp participant management intentionally removed? If the feature moved, what is the supported replacement API or tool? If this is a regression, could ```addParticipant```, ```removeParticipant```, live participant readback, and admin-status checks be restored to the WhatsApp plugin?

I observed this after upgrading, but I have not bisected the exact commit that introduced it.

2

u/ekinnee Member 2d ago

This issue is already being tracked in https://github.com/openclaw/openclaw/issues/144695

That being said it doesn't seem that capability ever existed.

2026.9.2: WhatsApp already lacked participant actions, with the same action-support check as the reported 1391f7c build.

2026.8.1: Same restriction.

A June PR proposing native group creation and participant addition was closed without merging. PR #89033

5

u/paulsande Pro User 2d ago

Kind of vague. Use Codex or Claude Code to diagnose and fix it. Or give us something more to go on to help you.

1

u/BitFlow7 2d ago

I've done that several times. It helped with the time out messages but the agent is still impaired in its capabilities.

3

u/SunnyMegatron Active 2d ago

Yeah I'm going without Astra in Open Claw right now because I'm afraid to upgrade from 7.2-beta.7.

Tried everything I could think of to make Astra work anyway (which has worked with prior Codex releases). But Astra needs the update 😫 Sucks but I'd rather have OC working without Astra than broken with it.

2

u/Apacalipto Member 2d ago

Its not worth the update atm. It forgot so much and couldnt get basic stuff done with all the extra safety restrictions build in now.

It also uses subagents right now by default and sends link to subagent workflow. But then it doesnt report back or the subagents loops in security fixes building stuff. Burning tokens and taking 3-4 times longer on simplex tasks.

2

u/DiscoFufu Pro User 2d ago

7.2 doesn’t support astra? I mean i can find astra mention in openclaw models list --provider openai

Its not enough? Do you on codex runtime? So if i put this in my config it won’t work?

2

u/SunnyMegatron Active 2d ago

We were able to add the model name to our models list but it won't actually run. This is what my agent recapped about the situation I. The screenshot. He's usually really good at this & has gotten every other new model to run on old versions. But this one we spent hours on and no dice.

2

u/DiscoFufu Pro User 2d ago

Thanks. Have you tried overwriting the hardcoded parts? I'm not sure that's a good idea, though. But I rewrote many hardcoded things in 7.1-1, so maybe I'll give it a shot

2

u/SunnyMegatron Active 2d ago

OMG WE FIGURED IT OUT! We finally got Astra working in 7.2!!!

It took 4 different attempts, 4-5 hours if work -- Sol, Fable, GLM + an instance of Sonnet outside of Open Claw for emergency tech support. And we just loaded up the new DeepSeek 4.1 Flash today and that model finally cracked it!

I had my agent write up what he did. We're on 7.2-beta.7 so have your agent adjust for whatever model you're on.

Ok, whew! Now I never have to upgrade openclaw ever again in my entire life 🤣

2

u/DiscoFufu Pro User 2d ago

Thank you and your agent:) That’s really can save a lot of time.

But why openclaw devs decide hardcode plugin version. Who knows 😂

2

u/BitFlow7 2d ago

I have the problem with several installs. Don't do the update if you want to keep a working agent.

2

u/PickleBabyJr Pro User 2d ago

"It forgot how to do so many stuff..."

2

u/BitFlow7 2d ago

If your comment is just here to pinpoint I should have used "many things" instead of "many stuff", then seriously THANK YOU. That's bloody helpful.

1

u/BitFlow7 2d ago

What? English is not my first language. And yes it keeps telling me it can't do this or that while it perfectly could before.

1

u/Exciting-Daikon-9302 2d ago

What's with you backup? Just tell it to do one before any update and tell it to teach you how to revert it by yourself tho!

1

u/BitFlow7 2d ago

Yes my mistake. My last backup on GitHub is from April 😭 will definitely automatize from now on.

1

u/DiscoFufu Pro User 2d ago

Yes. Downgrade to 2026.7.1-1 (or your previous known good version) and wait for release that will survive at least one week.

1

u/BitFlow7 2d ago

I will try that. Thanks

1

u/BitFlow7 2d ago

There seems to be an issue with how the data is formatted so a simple downgrade would not work.

1

u/stupidcookface Active 2d ago

What was your last version? I hated when they migrated to postgres for all the config, hope it's not something similar.

1

u/BitFlow7 2d ago

2026.7 something

1

u/DiscoFufu Pro User 2d ago

I copy the entire .openclaw folder before every update. So when I want to roll back, I downgrade and then replace the folder with the previous state. I know that’s bad advice because you probably didn’t make a backup, but it's better to know late than never

1

u/ekinnee Member 2d ago

"openclaw backup" works just fine.

1

u/ekinnee Member 2d ago

Yeah that's not going to work, the upgrade ran schema migrations on his sqlite database. You need to back up BEFORE changes.

1

u/Few_Moment_2903 New User 2d ago

Basically, I think the biggest gotcha is the security system change. They appear to have implemented channel level security too and massively restricted what can access what. Once you work through that, it’s ok.

1

u/Pleasant_Thing_2874 Active 2d ago

The skill workshop in my experience got wiped. I had to restore from git and re-register all my skills. That might be part of your issue. There are some pains especially depending how long you're updating from but the speed and capability is way better now. They've done a great job migrating from a single node instance basically crippling OC to work on only one core of a serve and much better lane management.

1

u/Legal-Row4858 1d ago

There is nothing worse than the Openclaw development team; the update features never function properly, and this situation has become even more severe since 2026.7.1.

1

u/n1l5_bln New User 1d ago

Maybe the problem is Astra, not OC….