Fix: Committed .grok/settings.json bypasses workspace trust and controls sandbox security posture

[superagent-security-dev]

Summary

Read sandbox mode and sandbox settings from user settings only (not the committed project file), consistent with the project-hooks and MCP exclusion.

Finding

Committed .grok/settings.json bypasses workspace trust and controls sandbox security posture

Generated by Superagent from the proposed patch for this finding.

---

Note

Low Risk
Narrow security hardening with predictable behavior change: project sandbox keys in .grok/settings.json are ignored; teams relying on committed sandbox config must move those values to user settings.

Overview
Sandbox mode and sandbox settings now come only from user settings (~/.grok/user-settings.json), not from the repo-committed .grok/settings.json.

getCurrentSandboxMode() no longer reads project.sandboxMode. getCurrentSandboxSettings() no longer merges project.sandbox with user settings and returns user.sandbox ?? {} only. This matches the existing policy for project hooks and MCP: committed project config is treated as untrusted for security-sensitive behavior.

^{Reviewed by Cursor Bugbot for commit f1e0b44. Configure here.}

[open-cla]

Contributor License Agreement

All contributors are covered by a CLA.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.