In-app configuration changedthird-party/claude-desktop/in-app-configuration

The first capture of this source. The page was already there, and this is what it said.

# In-app configuration

> Build, test, and export a Claude Desktop on 3P configuration from inside the app, with validation and per-provider guidance

The in-app configuration window is the recommended way to configure Claude Desktop for third-party inference. It validates values as you enter them, shows exactly which fields your inference provider requires, tests the connection against your endpoint, and computes the network egress allowlist for your settings, so you don't have to hand-edit JSON, plists, or registry keys.

## Open the configuration window

From the macOS menu bar (or on Windows, 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…**.

<Frame caption="The in-app configuration window, showing the Connection section for a gateway provider.">
  <img src="https://mintcdn.com/claude-ai/kVj7_7KF4fI3bEAn/images/third-party/in-app-configuration-window.png?fit=max&auto=format&n=kVj7_7KF4fI3bEAn&q=85&s=c3f15a85dea85082bc6dbc9459e6a974" alt="Claude Desktop in-app configuration window with the sidebar of setting groups on the left and the Connection form on the right." width="1812" height="1462" data-path="images/third-party/in-app-configuration-window.png" />
</Frame>

The sidebar groups settings the same way the [configuration reference](/docs/third-party/claude-desktop/configuration) does. Fill in **Connection** first, then work down through the sections your deployment needs.

## Apply locally or export for a fleet

Use **Apply locally** to write the configuration to this device only and relaunch into it. This is the [single-machine setup](/docs/third-party/claude-desktop/installation#single-machine-setup) path for evaluation and pilots.

Use the **Export** menu to generate deployment artifacts for a fleet:

| Export option               | Use with                                                                                            |
| --------------------------- | --------------------------------------------------------------------------------------------------- |
| `.mobileconfig` profile     | Jamf or any macOS MDM                                                                               |
| `.reg` policy file          | Intune, Group Policy, or any Windows MDM                                                            |
| ADMX template (`.zip`)      | Intune or Group Policy; a schema-only template, you enter values in the management console          |
| Profile Manifest (`.plist`) | Jamf, ProfileCreator, or similar macOS tools; a schema-only template, you enter values in your tool |
| Bootstrap JSON              | The response body for a [bootstrap server](/docs/third-party/claude-desktop/bootstrap)                   |
| Egress allowlist            | Your firewall or network team                                                                       |

See [Deploy with MDM](/docs/third-party/claude-desktop/mdm) or [Deploy with a bootstrap server](/docs/third-party/claude-desktop/bootstrap) to distribute what you exported.

When a managed profile is already present on the device, the window opens in read-only mode and shows the deployed values. Author new configurations from a device without a managed profile.

No line in this hunk matches that.