Plugin-provided settings now appear in /config, with their values redacted in telemetry
The /config (Settings) menu now merges in configuration entries provided by plugins, with per-entry visibility tracking and asynchronous refresh. New fields that offer a fixed set of choices but also accept a plugin-provided value now open a text-edit flow when selected. The tengu_config_changed telemetry event now records plugin-provided values as the placeholder plugin_field instead of logging the actual value.
This lets plugins surface their own settings inside the standard /config interface rather than requiring separate configuration, while keeping plugin-supplied values out of telemetry logs.
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.