Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] [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#45083•Fetched 2026-04-09 08:11:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
olehsh-dataforestolehsh-dataforest
Participants
olehsh-dataforestolehsh-dataforest
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When Claude starts implementing changes to a file it prompts whether I should allow it to edit the file but I can't skip out this prompt again unless I allow all editing. It's all or nothing. I'd like some in between and current options don't support this.

Today when Claude wants to edit a file it prompts us with these three choices: 1. Yes 2. Yes, allow all edits during this session (shift+tab) 3. No

If we don't allow access to all edits, it will prompt us repeatedly, for this file and for other files in the same directory. Stopping productivity by pausing for user intervention.

Proposed Solution

Offer two additional options that cover those scenarios, e.g. 1. Yes 2. Yes, allow all edits during this session (shift+tab) 3. Yes, allow edits for all files in this directory during this session 4. Yes, allow all edits for this file during this session 5. No

Alternative Solutions

When the user tabs on '1. Yes' and types "allow all edits for this file during this session", respect that instruction. Currently, Claude ignores this directive and instead it re-prompts. The same for "allow edits for all files in this directory during this session".

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

Example scenario:

  1. Claude and I agree to a change that requires touching all test cases in a large number of files in a directory.
  2. It shows me the first change and I'm good with it so I press 1 for yes I don't want to allow it to edit any files outside this directory
  3. Claude prompts me again for more changes in the same file and/or the same directory. My only choice is to approve each change or approve all changes.

Additional Context

It's pretty clear, the more files and directories you have and the more changes you have, the more annoying this limitation is.

extent analysis

TL;DR

Implement a customizable userTurnIndicator option in the settings.json file to improve readability of conversation transcripts in Claude Code.

Guidance

  • Introduce a new configuration option userTurnIndicator in settings.json to allow customization of the user message prefix.
  • Update the UI rendering to use the specified text and ANSI color for the user turn prefix.
  • Ensure the new configuration option is consistent with the existing statusLine customization pattern.
  • Test the new feature with different customizations to verify its effectiveness in improving transcript readability.

Example

{
  "userTurnIndicator": {
    "text": ">>>",
    "color": "green"
  }
}

Notes

The proposed solution builds upon the existing infrastructure for terminal color and text configuration in Claude Code, making it a low-effort but high-impact improvement.

Recommendation

Apply workaround by implementing the proposed userTurnIndicator option, as it provides a flexible and consistent way to customize the user message prefix, improving readability and navigation through long conversation transcripts.

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…
#parallel task#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING