/config now shows which plugin a setting comes from, and organizations can lock those settings
When a setting in /config was provided by a plugin (via that plugin's own configuration), the settings list now shows a small · <plugin> label next to it naming the source plugin.
Such plugin-provided settings can now also be locked, meaning a user can't change them, when they're set through an organization's managed settings or through a session's --settings option. Locking shows a specific message explaining which source locked the setting.
This makes it clear where a given setting is coming from when plugins are involved, and gives organizations a way to enforce plugin configuration choices that users can't override locally.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
With `disableEssentialTelemetry`, `disableNonessentialTelemetry`, `disableNonessentialServices`, and `disableAutoUpdates` all set to `true`, the desktop application makes **no outbound connections to Anthropic-operated hosts at runtime**. …third-party/claude-desktop/telemetry see the edit
| An estimated cost in US dollars for each conversation and model. The app calculates the estimate on the device, at Anthropic list prices or at the rates you set under **Models** on the **Connection** page, and labels which it used (`list…third-party/claude-desktop/admin-console see the edit
Anthropic's documentation has since written up /config, on Deploy with Enterprise Admin Console.