[FEATURE]
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Feature Request: Cross-file find and replace tool for Claude Code
I use Claude Code daily on a large Rust codebase. When I ask Claude to rename something - a config field, a function parameter, a YAML key - it has to make separate Edit tool calls for every occurrence in every file. A simple rename across 4 files just took 8 sequential edits.
It would be great if Claude Code had a cross-file find-and-replace tool, similar to Ctrl+Shift+H in VS Code. One call to replace a string across all matching files instead of editing them one by one.
For example, something like:
FindAndReplace(
pattern: "max_port_attempts",
replacement: "port_scan_range",
glob: "**/*.{rs,yaml}",
preview: true
)
This comes up constantly with refactors, renames, and config changes. It would save a lot of time and context window.
Proposed Solution
Feature Request: Cross-file find and replace tool for Claude Code
I use Claude Code daily on a large Rust codebase. When I ask Claude to rename something - a config field, a function parameter, a YAML key - it has to make separate Edit tool calls for every occurrence in every file. A simple rename across 4 files just took 8 sequential edits.
It would be great if Claude Code had a cross-file find-and-replace tool, similar to Ctrl+Shift+H in VS Code. One call to replace a string across all matching files instead of editing them one by one.
For example, something like:
FindAndReplace(
pattern: "max_port_attempts",
replacement: "port_scan_range",
glob: "**/*.{rs,yaml}",
preview: true
)
This comes up constantly with refactors, renames, and config changes. It would save a lot of time and context window.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
Performance and speed
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗