[BUG] Workspace trust not persisted between sessions + remote-control fails (Windows/Git Bash)

[shin729]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Workspace trust dialog appears every session even after accepting, and claude remote-control fails with "Workspace not trusted" error.

What Should Happen?

Workspace trust should be persisted after first acceptance, and claude remote-control should work without requiring re-acceptance every session.

Error Messages/Logs

Steps to Reproduce

1. Open Git Bash (MINGW64) on Windows
2. Run claude in C:\Users\biets
3. Accept the workspace trust dialog
4. Exit claude
5. Run claude again in the same directory
6. Trust dialog appears again (trust was not saved)
7. Run claude remote-control --name "xxx" → fails with "Workspace not trusted" error

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

v2.1.112

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Workspace trust dialog asks on every session startup, doesn't persist acceptance #43958
2. [BUG] Workspace trust not persisting in Claude Code CLI - MCP servers fail to load despite accepting trust prompt #12227
3. [BUG] Claude on native Windows repeatedly asks to trust folder #3366

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #43958.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.