claude-code - 💡(How to fix) Fix Claude ignores exact user-specified names and shortens/interprets them instead [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55074Fetched 2026-05-01 05:46:54
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Root Cause

  • Users should never have to repeat an explicit name more than once
  • Claude should treat user-provided names as exact strings, not as suggestions to be interpreted or shortened
  • This is especially harmful for ADHD users who already have to repeat themselves more than neurotypical users and should not have that burden compounded by an AI that ignores explicit instructions
RAW_BUFFERClick to expand / collapse

Problem

When a user specifies an exact name — for a skill, command, file, or any artifact — Claude defaults to a shorter or interpreted version instead of using the user's exact words. This happens even when the user repeats the name multiple times.

Example from real session

User said "sync me up" as the skill name — stated clearly, 4 separate times across the conversation. Claude named the skill sync anyway on the first build, then had to be corrected repeatedly before using the correct name sync-me-up.

Why this matters

  • Users should never have to repeat an explicit name more than once
  • Claude should treat user-provided names as exact strings, not as suggestions to be interpreted or shortened
  • This is especially harmful for ADHD users who already have to repeat themselves more than neurotypical users and should not have that burden compounded by an AI that ignores explicit instructions

Expected behavior

When a user says "call it X" or uses a name phrase, Claude uses that exact phrase — no shortening, no reinterpreting, no defaulting to a "cleaner" version — unless the user explicitly asks for a suggestion.

Submitted on behalf of

A Claude Code user (Oak Park Construction).

extent analysis

TL;DR

The issue can be addressed by modifying Claude's naming logic to prioritize exact user input over interpreted or shortened versions.

Guidance

  • Review Claude's current naming logic to identify where the shortening or interpretation of user input is occurring.
  • Consider adding a flag or parameter to indicate when a user has explicitly provided a name, ensuring that it is used verbatim.
  • Evaluate the conversation flow to determine how repeated user input can be handled to avoid requiring users to repeat themselves.
  • Investigate potential edge cases where exact naming may conflict with existing functionality, such as filename limitations or command parsing.

Example

No specific code example can be provided without more context on Claude's implementation, but a possible approach could involve adding a useExactName flag to the skill creation process.

Notes

The solution may require balancing exact user input with potential technical limitations or constraints, such as character limits or reserved words.

Recommendation

Apply a workaround to prioritize exact user input for naming, as this aligns with the expected behavior and user needs, especially for users who may require accommodations.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When a user says "call it X" or uses a name phrase, Claude uses that exact phrase — no shortening, no reinterpreting, no defaulting to a "cleaner" version — unless the user explicitly asks for a suggestion.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Claude ignores exact user-specified names and shortens/interprets them instead [1 participants]