OpenClaw 3.31 Update Resets Agent Permissions and Settings

What Changed in OpenClaw 3.31
The OpenClaw 3.31 update introduced significant changes to how agent permissions and settings are managed. According to user reports, the update automatically disabled multiple system components that previously functioned normally.
Specific Issues Reported
- All agents lost access to the user's computer after updating
- OpenClaw no longer sends approval requests for tool or PC access as it did previously
- Clicking "always allow" doesn't save permissions - agents revert to unapproved state within seconds
- All tools were switched off after the update
- All access permissions were switched off
- All sub-agents were switched off
Manual Fix Required
To restore functionality, users must manually re-enable everything through Settings:
- Navigate to Settings
- Go to AI & Agents section
- Manually turn on:
- All tools that provide access and permissions
- All sub-agents
Changed Permission Model
The update appears to have changed how permissions are handled. Instead of approving access requests as they come up during use, users now need to manually enable permissions in settings before agents can use them. This suggests a security-focused change where users must explicitly grant permissions rather than approving them reactively.
User Impact
The main frustration reported is the lack of clear communication about these changes. Users spent significant time troubleshooting what appeared to be a broken setup, only to discover the issue was buried in settings. The update effectively reset the entire agent configuration without warning.
Open Questions
Users are asking whether there are ways to preserve settings across updates to prevent similar disruptions in the future. The community is discussing whether this affects all users of version 3.31 or only specific configurations.
📖 Read the full source: r/openclaw
👀 See Also

OpenClaw contributor criticizes project's focus on pixel-perfect parity over modern features
A Reddit post from r/openclaw details how a contributor's PR addressing resolution scaling and high-refresh-rate support was rejected for deviating from the original engine's visual constraints, sparking debate about the project's direction.
Amazon Employees 'Tokenmaxxing' with MeshClaw AI Agents to Meet Usage Targets
Amazon developers are automating unnecessary tasks with the internal MeshClaw tool to inflate AI token consumption, after the company set weekly usage targets for 80% of devs and introduced internal leaderboards.

Forbes: The AI Layoff Bill Is Coming Due — CTOs Will Pay Twice
Forbes argues that the cost of AI-driven layoffs will hit companies twice: first in severance and morale, then in rehiring when the expected efficiency gains don't materialize.

Solo Dev Builds 35-Module Household SaaS with Claude — Workflow Deep Dive
A senior engineer with 25 years experience built a full household-management SaaS (35 modules, Vite + Netlify + Supabase) solo using Claude and Claude Code. Key pattern: investigate-then-fix, not code-first.