claude-code - 💡(How to fix) Fix [BUG] Trust settings couldn't be saved on Windows after update to 1.3883.0 [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52003Fetched 2026-04-23 07:39:10
View on GitHub
Comments
3
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4commented ×3

Error Message

After updating to 1.3883.0, clicking "Trust Workspace" shows error 4. See error: "Trust settings couldn't be saved"

Root Cause

Root cause suspected: CodexSandboxUsers group has only RX permission on .claude.json — cannot write trust settings after update reset file permissions.

RAW_BUFFERClick to expand / collapse

Version: 1.3883.0 (Windows MSIX) OS: Windows 11

Description: After updating to 1.3883.0, clicking "Trust Workspace" shows error "Trust settings couldn't be saved" and app is completely blocked. This worked fine before the update.

Root cause suspected: CodexSandboxUsers group has only RX permission on .claude.json — cannot write trust settings after update reset file permissions.

hasTrustDialogAccepted is already true in .claude.json but app still blocks.

Steps to reproduce:

  1. Update Claude Desktop to 1.3883.0 on Windows
  2. Open any workspace (previously trusted or new)
  3. Click "Trust Workspace"
  4. See error: "Trust settings couldn't be saved"
  5. App is completely blocked, cannot proceed

Expected: Trust is saved, app proceeds normally Actual: App blocked completely

extent analysis

TL;DR

The issue can likely be resolved by adjusting the permissions of the .claude.json file to allow write access for the CodexSandboxUsers group.

Guidance

  • Verify the current permissions of the .claude.json file to confirm that the CodexSandboxUsers group only has read permission (RX).
  • Check if the hasTrustDialogAccepted value in .claude.json is indeed true, as this might indicate a separate issue.
  • Attempt to manually adjust the permissions of .claude.json to include write access for the CodexSandboxUsers group and see if this resolves the issue.
  • If manual permission changes are not feasible, consider using a different approach to manage trust settings, such as using a different file or storage mechanism.

Example

No code snippet is provided as the issue seems to be related to file system permissions rather than code.

Notes

The provided information suggests a permissions issue, but it's unclear if this is the only contributing factor. Further investigation may be necessary to fully resolve the issue.

Recommendation

Apply workaround: Adjust the permissions of the .claude.json file to allow write access for the CodexSandboxUsers group, as this directly addresses the suspected root cause.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING