[BUG] /plugin configure: Enter on a sensitive userConfig field exits the dialog ("No configuration changes.") — token can never be entered (v2.1.198, macOS)

Summary

In the /plugin configure dialog, pressing Enter on a sensitive: true userConfig field does not open a text input. The dialog exits back to the prompt and prints No configuration changes. There is no way to type a value, so a plugin token can never be entered through the UI. Tab does not advance/open the field either.

This makes it impossible to configure any plugin that uses userConfig with sensitive: true — which is the only secure input surface plugins have for secrets.

Environment

• Claude Code v2.1.198 (also reproduced on earlier 2.1.x)
• macOS (Darwin 24.6.0), terminal CLI (native install)
• Reproduced with the official FlutterFlow plugin (FlutterFlow/flutterflow-claude marketplace), but any plugin with a sensitive: true string option should reproduce it.

Steps to reproduce

1. ```

claude plugin marketplace add FlutterFlow/flutterflow-claude
claude plugin install flutterflow@flutterflow
``
(The plugin's manifest declares userConfig.api_token with "type": "string", "sensitive": true`.)

1. Run /plugin configure flutterflow@flutterflow.
2. The dialog renders correctly: Plugin options, cursor on ❯ FlutterFlow API token, a Save configuration row below, footer ↑/↓ to move · Enter to continue · Esc to cancel.
3. With the token field selected, press Enter.

Expected

A masked text input opens so the user can type/paste the token, then save.

Actual

The dialog closes immediately and Claude Code prints:

/plugin configure flutterflow@flutterflow
  ⎿ No configuration changes.

No input was ever shown. ↑/↓ and Esc work; Enter and Tab never open the field.

Please don't auto-close this as a duplicate — the previous report was mis-triaged

This exact bug was reported in #51538 (/plugin Configure UI: Tab and Enter don't advance between userConfig fields). The triage bot closed it as a duplicate of #23612, which is a different bug (keyboard navigation in the /config panel). #23612 was in turn auto-closed as a duplicate of #8378 — a third, unrelated bug (Settings TUI tabbing flipping boolean values on Linux) that was fixed in v2.0.9 (October 2025). All three issues are now closed and locked.

Net effect: the /plugin configure input bug is tracked nowhere, while it still reproduces on the latest release. This issue is the re-file that the auto-lock messages request.

Related (but distinct) issues

• #62442 — sensitive userConfig values not persisted across restarts (closed as not planned). Even when a value does get stored, it may not survive a restart, so the whole sensitive: true feature is currently unusable end-to-end.
• #39455 — userConfig not prompted on plugin enable (open).

Impact

This blocks the documented onboarding of the official FlutterFlow plugin (and any plugin needing an API key): users install the plugin, run /plugin configure, and hit a dead end. The only workaround is asking users to hand-write credential files in a separate terminal, which defeats the purpose of userConfig secure storage.