Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Plan mode auto-generated filename can produce inappropriate-sounding names [1 comments, 2 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#52836•Fetched 2026-04-25 06:19:36
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
djacuradjacura
Participants
djacuradjacuragithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1unlabeled ×1

Code Example

twinkly-seeking-cocke.md

---

That's the full plan — 7 steps across 9 files, all laid out with before/after for each change. Take a look and let me know if you'd like to adjust anything, or if we're
  good to start executing step by step.
  ⎿  Tool use rejected with user message: that file name is awful where did you get that from ? that seems really inappropiate ?

⏺ That name was auto-generated by the system — I agree, not great. Let me move it to something sensible.

⏺ Bash(cp /Users/djacura/.claude/plans/twinkly-seeking-cocke.md /Users/djacura/.claude/plans/fft-63286-sim-config-folder.md && rm /Users/djacura/.claude/plans/twinkly-…)
  ⎿  Done
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues for similar behavior reports
  • This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

Plan mode auto-generated filename can produce inappropriate-sounding names

What Claude Actually Did

When entering plan mode, Claude Code auto-generates a random filename for the plan file using a pattern like adjective-verb-noun. In one instance, the generated filename was:

twinkly-seeking-cocke.md

While "Cocke" is likely sourced from the computer scientist John Cocke, the resulting combination reads inappropriately and caused concern.

Expected Behavior

The random name generator should either:

  • Filter out words/combinations that could be read as inappropriate
  • Use a safer word list that avoids ambiguous surnames or words
  • Allow users to configure or override the naming pattern

Files Affected

twinkly-seeking-cocke.md

Permission Mode

I don't know / Not sure

Can You Reproduce This?

No, only happened once

Steps to Reproduce

Steps to Reproduce

  1. Enter plan mode (via EnterPlanMode)
  2. Observe the auto-generated plan filename in the system message

Claude Model

Opus

Relevant Conversation

That's the full plan — 7 steps across 9 files, all laid out with before/after for each change. Take a look and let me know if you'd like to adjust anything, or if we're
  good to start executing step by step.
  ⎿  Tool use rejected with user message: that file name is awful where did you get that from ? that seems really inappropiate ?

⏺ That name was auto-generated by the system — I agree, not great. Let me move it to something sensible.

⏺ Bash(cp /Users/djacura/.claude/plans/twinkly-seeking-cocke.md /Users/djacura/.claude/plans/fft-63286-sim-config-folder.md && rm /Users/djacura/.claude/plans/twinkly-…)
  ⎿  Done

Impact

High - Significant unwanted changes

Claude Code Version

2.1.66 — you can add that to the issue under Environment if you'd like.

Platform

Anthropic API

Additional Context

No response

extent analysis

TL;DR

The issue can be mitigated by filtering out words or combinations that could be read as inappropriate from the auto-generated filename pattern.

Guidance

  • Review the word list used for auto-generating filenames to identify potential sources of inappropriate combinations.
  • Consider implementing a filter to exclude surnames or words that could be misinterpreted.
  • Allow users to configure or override the naming pattern to prevent similar issues.
  • Test the auto-generated filename feature with various inputs to ensure the filter is effective.

Example

No code snippet is provided as the issue does not contain sufficient technical details.

Notes

The solution may require modifications to the Claude Code's naming pattern generation algorithm or the addition of a filtering mechanism.

Recommendation

Apply a workaround by filtering out potentially inappropriate words or combinations from the auto-generated filename pattern, as a permanent fix may require significant changes to the underlying algorithm.

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…
#api#model save/load#optimization#mixed precision#training loop

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 Plan mode auto-generated filename can produce inappropriate-sounding names [1 comments, 2 participants]