Open the configuration window
From the macOS menu bar (or on Windows and Linux, the application menu ☰ in the top-left of the sign-in screen), go to Help → Troubleshooting → Enable Developer Mode, then Developer → Configure Third-Party Inference…. If you turn on Developer mode while the app is running a third-party configuration, it stays on across restarts. If you turned it on before that, the Developer menu is gone once the app relaunches into a third-party configuration, for example after Apply Changes. Go to Help → Troubleshooting → Enable Developer Mode again, and it stays on from then on. If the configuration setsdeveloperModeEnabled to false, neither that item nor the Developer menu appears.
To turn Developer mode off again, go to Developer → Open Developer Config File, change "allowDevTools": true to false in the file that opens (or delete the file), save it, then quit and reopen Claude Desktop. The Developer menu is gone on the next launch.

The in-app configuration window, showing the Connection section for a gateway provider.
Apply locally or export for a fleet
Use Apply Changes to write the configuration to this device only and relaunch into it. This is the single-machine setup path for evaluation and pilots. Use the Export menu to generate deployment artifacts for a fleet:
See Deploy with MDM or Deploy with a bootstrap server to distribute what you exported.
When a managed profile on the device sets any key other than the app-behavior keys and the keys treated like them, the window opens in read-only mode and shows the deployed values. Its Export menu offers JSON config (redacted), a file to import into the Enterprise Admin Console. This option requires Claude Desktop 4.23118.0 or later. Author new configurations from a device without such a profile.