Switching output style in /config is now safer for shared sessions and won't let you reselect the current style
The output-style picker in the /config settings panel now behaves more carefully when changing styles:
- If the session might not belong to its original owner, it checks that a requested custom style is actually valid before allowing the switch.
- If you pick the style that's already active, it now just tells you so instead of doing anything.
- If the capability needed to save the change locally (
localSettings) isn't available, it now errors out clearly before trying to save, rather than failing partway through.
These changes prevent confusing failures: a shared or non-owner session can't be pointed at an invalid style, picking your current style no longer does pointless work, and a missing save capability is caught up front instead of causing a silent or partial failure.
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.