openclaw - 💡(How to fix) Fix 2026.4.1 exec approval mechanism completely broke existing single-operator setups [2 comments, 3 participants]

2026.4.1 update introduced sandboxing and exec approval changes that completely broke exec for all existing single-operator setups.

What happened:

After updating to 2026.4.1, every exec command immediately fails with:

Exec approval registration failed: Error: gateway closed (1008): pairing required

Even though the gateway is running and healthy, the exec tool cannot register commands without manual approval every single time.

Expected behavior (before this update):

• exec worked out of the box for local/loopback connections
• macOS showed a system permission dialog for folder/app access when needed, which was acceptable
• No additional per-command approval workflow required

What changed in 2026.4.1:

• Forced exec approval mechanism that requires manual /approve for every single command
• No migration guide provided
• No documented way to disable or opt out
• Existing configs that worked fine are now completely broken with no clear fix
• This affects ALL existing users upgrading to 4.4.1

Steps to reproduce:

1. Have a working openclaw setup pre-4.4.1
2. Update to 2026.4.1
3. Try running any exec command
4. Every command fails with pairing required error despite gateway being healthy

Impact:

• Completely blocks automated workflows
• Breaks existing single-user/local setups
• User had to go through 4+ manual /approve interactions just to run basic commands

Requested fix:

Either:

1. Provide a documented config option to disable exec approvals for local/loopback setups
2. Auto-approve exec commands when running in single-operator mode
3. Provide a better migration path for existing users upgrading to 4.4.1

This is a regression that affects all existing users upgrading to 4.4.1.