[Bug] Claude Code Desktop crashes on remote-delivered managed settings with bundled runtime 2.1.219

Status Closed — duplicate
Reported on v2.1.219
Maintainer reply None cached
Activity 4 comments · opened Jul 29, 2026 · closed Aug 25, 2026

Bug Description
Claude Code Desktop crashes on all new Code sessions when managed settings are delivered via admin console (remote) Desktop app: latest, bundled runtime 2.1.219. macOS. Standalone CLI 2.1.220 loads the same remote policy without issue — /status shows Enterprise managed settings (remote), 6 MCP servers connected. Identical policy (SHA-256 8cc515db787d4e22f89b2cb46144fb17f2511bae348fdbff16b1325e44049d21) works when written to /Library/Application Support/ClaudeCode/managed-settings.json. Bisected 8 staged configs — all pass as local files, including the full 313-rule policy. Backend completes normally (stop_reason: end_turn, valid assistant response in ~/.claude/projects/.../<cliSessionId>.jsonl) while the client renders "Claude Code crashed." No OS crash report generated (checked ~/Library/Logs/DiagnosticReports and Console.app). Remote settings write nothing to disk, so no local artifact exists to diff. Config includes allowManagedMcpServersOnly: true, disableSideloadFlags: true, 13 allowedMcpServers, 313 permission rules. Suspected: Desktop's bundled 2.1.219 runtime mishandles remote-delivered managed settings; fixed or absent in 2.1.220.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.220
  • Feedback ID: 2785d9dd-5dea-4433-bc18-f0b91d6e5c9a

Errors

[]

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗