PromptHint: engine draws " · " after the mode label even when a hook's rewritten hint is empty
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by locating PromptHintPart and reading how it draws the mode label and dim separator when a render hook rewrites the hint. Reproduce the issue using the ui.render hook from the report with an empty hint in bypass permissions mode. Done when the separator is omitted for an empty rewritten hint and remains correct for non-empty hints.
Written by the indexing model from the issue text.
Description
Version: Claude Code 2.1.311, macOS, terminal surface
What happens: A mod hooks ui.render on { component: 'PromptHint' } and strips (shift+tab to cycle) from e.props.hint. In bypass permissions mode the engine has already removed the mode label from hint, so the rewritten hint is "". The engine still draws [mode label] · [hint], which leaves a dangling separator: ⏵⏵ bypass permissions on ·
Expected: When the rewritten hint is empty, no separator is drawn.
Cause: In PromptHintPart, the mode label and the dim " · " are drawn together whenever the site reports the line as rewritten, whatever the hint's text. A mod can't get around it: hint, tail and a custom tree all draw to the right of the separator, and an absolutely positioned Box can't reach it because the site clips it.
Repro:
on('ui.render', { component: 'PromptHint' }, ($, e, next) =>
next({ ...e, props: { ...e.props, hint: '' } }))
Switch to bypass permissions mode (or any mode with a label) and look at the hint line under the prompt.
Suggested fix: Draw " · " only when the hint is non-empty.
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 25k
- Avg merge
- 16h 19m
- Merged PRs (30d)
- 5
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No 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.
More from anthropics/claude-code
-
area:vscode bug has repro platform:vscode platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anthropics/claude-code#111416 ·
-
area:docs area:security documentation enhancement platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/claude-code#111180 ·
-
area:ide enhancement platform:macos platform:vscode
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/claude-code#111172 ·
-
area:mcp bug has repro platform:linux platform:wsl
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anthropics/claude-code#111077 ·
-
area:cost area:mcp area:self-hosted-environments bug platform:linux
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
anthropics/claude-code#111048 ·
All issues in anthropics/claude-code
Similar issues
-
fix(resources): `flisk resources api` fails with a bare "too many arguments" and no hint; status, logs, down and networks already explain names are not positionalPossibly taken A pull request linked to this issue is open or already merged. Openarea: cli beginner beginner friendly bug community difficulty: easy dx easy first-timers-only good first issue hacktoberfest help wanted low-hanging fruit mentor available priority: P3 severity: low tech: typescript testing up-for-grabs ux
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
backlog-skill cat:docs documentation effort:s ready-for-agent sev:low
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LucasSantana-Dev/Lucky#3284 ·
Maintainers usually reply within 1 day
-
.aif still missing from the pipeline and library MIME maps, AUDIO_INPUTS, and search aliasesPossibly taken A pull request linked to this issue is open or already merged. Openarea: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
snapotter-hq/SnapOtter#5194 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
homarr-labs/homarr#7671 ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day