"Failed to persist policy" error despite correct permissions

(15 条评论) (0 个反应) (1 位负责人)TypeScript (13,657 个派生)batch import

area/coreeffort/smallhelp wantedkind/bugpriority/p2status/bot-triagedtype/bug

仓库指标

星标: (103,992 个星标)
PR 合并指标: (平均合并 4天 2小时) (30 天内合并 55 个 PR)

描述

What happened?

I am receiving the error "✕ Failed to persist policy for run_shell_command" when selecting "allow for all future sessions". I have verified the following: 1. Permissions: The directory ~/.gemini/policies is writable by my user. 2. Configuration: settings.json has "enablePermanentToolApproval": true. 3. File State: The auto-saved.toml file exists, is valid TOML, and is not locked by other processes. This appears to be an internal issue with the CLI's persistence logic or sandboxing constraints preventing the write operation. System: Linux (aarch64)

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

preference stored

Client information

CLI Version: 0.29.5
Git Commit: 2ef872e73
Session ID: 824fa46c-018a-4ba6-b765-1f305fd73dc6
Operating System: linux v22.21.1
Sandbox Environment: no sandbox
Model Version: gemini-3-pro-preview
Auth Type: oauth-personal
Memory Usage: 1.04 GB
Terminal Name: Unknown
Terminal Background: #0c0c0c
Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?