{"version":"2.1.269","anchor":"new-generic-textedit-settings-field-for-plugin-provided-co","canonical_anchor":"new-generic-textedit-settings-field-for-plugin-provided-co","heading":"New generic 'TextEdit' settings field for plugin-provided config values","tier":"use","area":"Plugin Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-generic-textedit-settings-field-for-plugin-provided-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New generic 'TextEdit' settings field for plugin-provided config values\n\nSettings screen gains a generic text-input field type for plugin-defined configuration values\n\n**What**\n\nThe 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.\n\n**Why**\n\nPlugin 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.\n\n- Area: Plugin Settings\n- Names: `\/config`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}