claude-code - 💡(How to fix) Fix [BUG] disableAutoUpdates should not lock the entire third-party inference UI [2 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#54647Fetched 2026-04-30 06:39:55
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2unlabeled ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Workarounds (all unsatisfactory)

Code Example



---

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadType</key>
            <string>com.anthropic.claudefordesktop</string>
            <key>PayloadIdentifier</key>
            <string>com.anthropic.claudefordesktop.updates</string>
            <key>PayloadUUID</key>
            <string>A1B2C3D4-E5F6-7890-ABCD-EF1234567890</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
            <key>disableAutoUpdates</key>
            <true/>
        </dict>
    </array>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadIdentifier</key>
    <string>com.yourorg.claude.updatepolicy</string>
    <key>PayloadUUID</key>
    <string>B2C3D4E5-F6A7-8901-BCDE-F12345678901</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>
RAW_BUFFERClick to expand / collapse

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?


Setting disableAutoUpdates = true via MDM causes Claude Desktop to lock the entire third-party inference settings UI as "Organization-managed" — even though no inference-related keys are configured. Admins who only want update control lose all user ability to self-configure inference without deploying a full MDM inference profile.


Problem statement

Claude Desktop reads MDM preferences from the com.anthropic.claudefordesktop domain on macOS. The moment any key is present in that domain — even a single disableAutoUpdates = true — the app treats the device as fully managed and marks the complete third-party inference configuration UI as read-only with an "Organization-managed" banner.

This is an all-or-nothing behaviour. There is no way to tell Claude Desktop "only this key is managed; everything else remains user-configurable."


<img width="1697" height="1043" alt="Image" src="https://github.com/user-attachments/assets/ae432189-d8eb-4151-94dd-8d6b3ccad3f4" />

What Should Happen?


Expected behaviour

The UI lock should be key-scoped, not profile-scoped. If only disableAutoUpdates is deployed via MDM, only the auto-update setting should appear as "managed". All other settings — including the full third-party inference configuration — should remain fully editable by the user.

This is already how macOS system preferences work in general: individual plist keys can be managed while others remain free.



Suggested solution

Introduce per-key locking in the UI. Each settings section should check independently whether the relevant MDM keys are set — not whether any MDM profile exists at all. Example logic:


Workarounds (all unsatisfactory)

  • Deploy a full inference configuration profile via MDM alongside the update key — high overhead for what should be a simple user-facing setting.
  • Block update URLs at the network/firewall level instead of using MDM keys — brittle and bypasses Anthropic's intended MDM mechanism.
  • Install Claude Desktop to ~/Applications instead of /Applications so the user has write access — removes fleet version control.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

  1. Deploy the following minimal .mobileconfig profile to a macOS device via MDM (e.g. Jamf, Kandji, Mosyle, Intune):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadType</key>
            <string>com.anthropic.claudefordesktop</string>
            <key>PayloadIdentifier</key>
            <string>com.anthropic.claudefordesktop.updates</string>
            <key>PayloadUUID</key>
            <string>A1B2C3D4-E5F6-7890-ABCD-EF1234567890</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
            <key>disableAutoUpdates</key>
            <true/>
        </dict>
    </array>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadIdentifier</key>
    <string>com.yourorg.claude.updatepolicy</string>
    <key>PayloadUUID</key>
    <string>B2C3D4E5-F6A7-8901-BCDE-F12345678901</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>
  1. Open Claude Desktop on the managed device.
  2. Enable Developer Mode via Help → Troubleshooting → Enable Developer Mode.
  3. Navigate to Developer → Configure third-party inference.
  4. Observe that every section shows the banner:

    "This configuration is managed by your organization. Contact your IT administrator to make changes."

  5. All fields are read-only. The user cannot configure any inference provider, gateway URL, or API key — despite no inference-related keys being present in the profile.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information


Impact: Any IT admin who deploys even a single MDM key (e.g. for update control) inadvertently breaks the self-service inference configuration flow for all users on managed devices. This is particularly painful in organisations that want update governance but do not (yet) use a centralised inference provider.

extent analysis

TL;DR

Introduce per-key locking in the UI to allow individual settings to be managed independently via MDM.

Guidance

  • Review the MDM profile deployment process to ensure that only the intended keys are being managed.
  • Modify the Claude Desktop application to check for MDM keys on a per-setting basis, rather than treating the entire configuration as managed if any key is present.
  • Consider implementing a more granular permission system to allow for finer-grained control over which settings are managed via MDM.
  • Test the modified application with different MDM profiles to ensure that the per-key locking behaves as expected.

Example

No code example is provided, as the issue requires changes to the Claude Desktop application's logic for handling MDM keys.

Notes

The suggested solution requires modifications to the Claude Desktop application, which may involve significant development and testing efforts. Additionally, the issue may be specific to the Anthropic API and macOS platform, and may not be applicable to other environments.

Recommendation

Apply a workaround by deploying a full inference configuration profile via MDM alongside the update key, although this is considered high overhead and not ideal. A better solution would be to modify the Claude Desktop application to support per-key locking, but this may require significant development efforts.

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

claude-code - 💡(How to fix) Fix [BUG] disableAutoUpdates should not lock the entire third-party inference UI [2 comments, 2 participants]