The Whatever

Your first follow for a shameful timeline.

[The Whatever @thewhatever]

@DavidSacks https://t.co/RU8jwruZsw

[The Whatever @thewhatever]

@AILayoffs Hey can you DM me? thanks.

[The Whatever @thewhatever]

@Budgetdog_ $PYPL is the most obvious long right now.

[The Whatever @thewhatever]

@Gutiiii83 @wassollichhier @openclaw Same. Figure anything out? Thinking I might have to downgrade to 5.7 aghh

[The Whatever @thewhatever]

@Kizzayyyyyyyy @Canucks @BatchHockey Zero chance.

[The Whatever @thewhatever]

@wealthmoose @grok is this post true?

[The Whatever @thewhatever]

@LeBlondModere @canindependent

[The Whatever @thewhatever]

@donjulioholo @AdolfoUsier @openclaw I ended up rolling back yesterday. But here is the actual fix it you haven't seen: https://t.co/2LCahXZpIp

[Vox @Voxyz_ai]

openclaw 3.31 seeing more approval prompts after upgrading? this is a security tightening, not a bug.

default exec policy is now allowlist + ask on-miss. anything not on the list prompts. gateway auth also tightened, local-direct needs explicit token config.

to fix it, make sure both layers are aligned. if they disagree, the stricter one wins:

agent config:
{
"tools": {
"profile": "full",
"exec": {
"security": "full",
"ask": "off"
}
}
}

~/.openclaw/exec-approvals.json:
{
"version": 1,
"defaults": {
"security": "full",
"ask": "off"
},
"agents": {}
}

tested this today on a live VPS running 3.31. after setting both layers to full + off and restarting the gateway, approvals stopped. openclaw approvals get confirmed defaults = security=full, ask=off.

on a node? make sure pairing is approved first. this release keeps node commands disabled until pairing is approved. haven't tested node-side yet, only verified gateway host.

not sure what these changes mean? leave the defaults. the strict mode is intentional.

[The Whatever @thewhatever]

@donjulioholo @AdolfoUsier @openclaw Same thing happened for me today. Frustrating!

[The Whatever @thewhatever]

Reservoir Ducks