## Description When configuring a plugin via `/plugin` → Installed → Configure Options, the dialog exits prematurely if any input field (URL, username, or password) contains the letter **n**. ## Steps to reproduce 1. Install a plugin that requires credentials 2. Run `/plugin` → Installed → plugin name → Configure Options 3. In any input field, type a value that contains the letter **n** 4. The dialog exits without saving ## Expected behavior The dialog should only exit when the user explici

Plugin configuration dialog exits when input contains the letter 'n'

Status Fixed / completed

Maintainer reply None cached

Workaround ✓ Mentioned in description ↑

Activity 4 comments · opened Apr 25, 2026 · closed Apr 27, 2026

Description

When configuring a plugin via /plugin → Installed → Configure Options, the dialog exits prematurely if any input field (URL, username, or password) contains the letter n.

Steps to reproduce

Install a plugin that requires credentials
Run /plugin → Installed → plugin name → Configure Options
In any input field, type a value that contains the letter n
The dialog exits without saving

Expected behavior

The dialog should only exit when the user explicitly cancels. Input values should be treated as literal strings regardless of their content.

Workaround

Copy-paste the full value and press Enter on Save configuration rather than typing character by character.

Environment

Platform: Linux
Shell: bash

View original on GitHub ↗

4 Comments

github-actions[bot] · 5 months ago

Found 2 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

0xbrainkid · 5 months ago

This looks like a keybinding / input-routing bug inside the configuration dialog rather than a plugin-specific problem. If typing a literal n is interpreted as a navigation or cancel signal while focus is inside a text field, then the UI is not respecting text-entry mode.

That makes credential entry especially brittle because users cannot reason about whether keystrokes are going to the field or to the surrounding dialog controls. The scary part is that it fails on common characters, not edge cases.

So the expected boundary should be strict:

while a text input has focus, keystrokes are treated as literal field content
dialog-level shortcuts only fire when focus is outside the field or when an explicit modifier/escape path is used

Otherwise configuration UIs become effectively nondeterministic for normal secrets/usernames/URLs, which is worse than an ordinary validation error because users cannot trust the input surface itself.

twishabansal · 5 months ago

I am facing the same issue. Also on, typing 'y', the cursor moves to the next userconfig entry.