{"version":"2.1.269","anchor":"plugin-provided-settings-fields-integrated-into-the-config","canonical_anchor":"plugin-provided-settings-fields-integrated-into-the-config","heading":"Plugin-provided settings fields integrated into the \/config (Settings) menu","tier":"use","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/plugin-provided-settings-fields-integrated-into-the-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin-provided settings fields integrated into the \/config (Settings) menu\n\nPlugin-provided settings now appear in \/config, with their values redacted in telemetry\n\n**What**\n\nThe `\/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.\n\n**Why**\n\nThis 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.\n\n- Area: Settings\n- Names: `\/config`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}