The settings interface (opened with /config) can now show a plain text-entry field for configuration values defined by a plugin, using the label, description, and validation rules the plugin provides. This joins the existing Output Style and Language picker fields, and all three now share a common helper that validates a change and applies it to the right settings file (localSettings or userSettings) before saving.
Plugin authors can define settings that need free-text values (not just picking from a list), and this gives Claude Code a built-in way to collect and validate them consistently, catching bad input ("Not a value it takes") before it gets saved.
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.