Form fields don't support mouse click / cursor placement for inline text editing

Open

#4,944 opened on Sep 22, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 65/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: shell
Domain: cli, frontend

Research direction

Look at the code handling the ask_user/elicitation tool form fields, likely in the UI or input layer of the CLI. Compare how the main prompt input handles mouse events and cursor placement. Identify the specific component or function that renders form fields and see where mouse interaction is missing. Test the fix by running the CLI and triggering a form to verify cursor placement works.

Written by the indexing model from the issue text.

Description

area:input-keyboard area:tools

Describe the bug
In the normal prompt input, users can click with the mouse to reposition the cursor and edit text inline (insert/delete at an arbitrary point). When answering a question inside an agent-presented form (ask_user/elicitation tool), this same interaction is not available — there's no way to click to place the cursor mid-text, forcing users to fall back to keyboard-only editing (or retyping) for anything beyond a short, simple answer.

Expected behavior
Text fields inside forms should support the same mouse-based cursor placement / inline editing behavior as the main prompt input, so editing a longer or partially-wrong answer doesn't require retyping it from scratch.

Additional context
This creates a jarring UX inconsistency: the interaction model a user has learned for the main prompt doesn't carry over once a form is shown, making the tool's behavior unpredictable depending on which UI mode is active.

Dominant language: Shell
Stars: 11.2k
Forks: 1.9k
Avg merge: 14h 16m
Merged PRs (30d): 6

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

wrapper-provision-jdk: require curl only when downloading a JDK Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

elastic/gradle-plugins#156 · Opened Sep 23, 2026
scripts/acceptance.sh times out: acceptance package needs longer than go test's 10m default Open

Priority/High ready-for-agent Severity/Major Type/Bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

wso2/wso2-cli#235 · Opened Sep 23, 2026
[Bug]: Documented CLI examples fail with argparse errors (profile export/import, backup restore, send, skills config/search, sessions show, kanban swarm, peer run, cron add) Open

comp/cli P3 type/docs

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

NousResearch/hermes-agent#119756 · 1 comment · Opened Sep 23, 2026
Canary builds are named after the release candidate, so npm ranks them above it Open

comp: build/pipeline type: bug version: current (v17+)

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

angular/angularfire#3766 · Opened Sep 23, 2026
cachyos-mango-noctalia: new version 1.4.0 Open

out-of-date

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

CachyOS/CachyOS-PKGBUILDS#1903 · Opened Sep 22, 2026

More Shell/Bash issues