What
Turning Claude-drafted feedback on or off goes through a single code path that also records the origin of the change, via: "card" when it came from the dismiss prompt and via: "config" when it came from /config.
Details
- Pairs with the new dismiss-time turn-off prompt and its
tengu_feedback_turnoff_prompt_shownandtengu_feedback_turnoff_prompt_declinedevents. - Declines accumulate in
feedbackDraftsTurnOffPromptDeclines; the prompt is suppressed after 2.
Evidence
tengu_feedback_turnoff_prompt_shown
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/config
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.
Added since
A small documentation edit on Telemetry and egress touched a line naming /config after this was published.
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
Confirmed since
Anthropic's documentation has since written up /config, on MCP, plugins, skills, and hooks.
| `.mcp.json` | MCP servers bundled with this plugin. A JSON object keyed by server name: `{"mcpServers": {"<name>": {"type": "http", "url": "...", "oauth": true}}}`. A remote entry uses `type` (`http` or `sse`), not `transport`, and suppo…third-party/claude-desktop/extensions see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /config, on MCP, plugins, skills, and hooks.