开启 elevated 后仍报 permission denied 的最小排障手册
针对“已开 elevated 但执行仍 permission denied”的常见场景,整理出可执行的四段式排查:开关、会话、执行位置与策略边界。
REDDITDiscovered 2026-02-12Author u/philly_mtl
Prerequisites
- Gateway config can be edited and restarted safely.
- Your sender account is expected to be in elevated allowlist.
Steps
- Run a baseline check: openclaw gateway status and confirm gateway is healthy before changing permissions.
- Set session-level elevated mode explicitly (/elevated ask or /elevated full) and verify it is acknowledged in the same session.
- Validate allowlist + provider mapping: ensure tools.elevated.allowFrom.<provider> includes your account and no per-agent override blocks it.
- Re-run the failing command from workspace path first; only then test host paths requiring elevated host execution.
- If still denied, inspect ask/security policy to confirm command is blocked by policy rather than missing elevated.
Commands
openclaw gateway statusopenclaw gateway restartopenclaw help/elevated ask/elevated fullVerify
Previously failing command now succeeds on an allowed path, and session status shows expected elevated mode.
Caveats
- /elevated on|ask does not force full security override; command can still be denied by policy.
- Avoid testing with sensitive root paths first; verify with harmless commands before high-risk operations.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗