Multi-Agent Coordinated Rename Refactoring
📝 Original Info
- Title: Multi-Agent Coordinated Rename Refactoring
- ArXiv ID: 2601.00482
- Date: 2026-01-01
- Authors: ** - Abhiram Bellur (University of Colorado, USA) - Mohammed Raihan Ullah (University of Colorado, USA) - Fraol Batole (Tulane University, USA) - Mohit Kansara (University of Texas at Dallas, USA) - Masaharu Morimoto (NEC Corporation, Japan) - Kai Ishikawa (NEC Corporation, Japan) - Haifeng Chen (NEC Laboratories America, USA) - Yaroslav Zharov (JetBrains Research, Germany) - Timofey Bryksin (JetBrains Research, Cyprus) - Tien N. Nguyen (University of Texas at Dallas, USA) - Hridesh Rajan (Tulane University, USA) - Danny Dig (University of Colorado, USA) **
📝 Abstract
The primary value of AI agents in software development lies in their ability to extend the developer's capacity for reasoning and action, not to supplant human involvement. To showcase how to use agents working in tandem with developers, we designed a novel approach for carrying out coordinated renaming. Coordinated renaming, where a single rename refactoring triggers refactorings in multiple, related identifiers, is a frequent yet challenging task. Developers must manually propagate these rename refactorings across numerous files and contexts, a process that is both tedious and highly error-prone. State-of-the-art heuristic-based approaches produce an overwhelming number of false positives, while vanilla Large Language Models (LLMs) provide incomplete suggestions due to their limited context and inability to interact with refactoring tools. This leaves developers with incomplete refactorings or burdens them with filtering too many false positives. Coordinated renaming is exactly the kind of repetitive task that agents can significantly reduce the developers' burden while keeping them in the driver's seat. We designed, implemented, and evaluated the first multi-agent framework that automates coordinated renaming. It operates on a key insight: a developer's initial refactoring is a clue to infer the scope of related refactorings. Our Scope Inference Agent first transforms this clue into an explicit, natural-language Declared Scope. The Planned Execution Agent then uses this as a strict plan to identify program elements that should undergo refactoring and safely executes the changes by invoking the IDE's own trusted refactoring APIs. Finally, the Replication Agent uses it to guide the project-wide search. We first conducted a formative study on the practice of coordinated renaming in 609K commits in 100 open-source projects and surveyed 205 developers, and then we implemented these ideas into CoRenameAgent. In our rigorous, multi-methodology evaluation of CoRenameAgent, we are using two benchmarks. First, on an established benchmark that contains 1349 renames, CoRenameAgent achieves a 2.3× F1-score improvement over the state-of-the-art. Second, on our new, uncontaminated benchmark of 1573 recent renames, it demonstrates a 3.1× F1-score improvement. By having CoRenameAgent 's automatically generated pull requests accepted into active open-source repositories, we provide compelling evidence of its practical utility and potential adoption.💡 Deep Analysis
Deep Dive into Multi-Agent Coordinated Rename Refactoring.The primary value of AI agents in software development lies in their ability to extend the developer’s capacity for reasoning and action, not to supplant human involvement. To showcase how to use agents working in tandem with developers, we designed a novel approach for carrying out coordinated renaming. Coordinated renaming, where a single rename refactoring triggers refactorings in multiple, related identifiers, is a frequent yet challenging task. Developers must manually propagate these rename refactorings across numerous files and contexts, a process that is both tedious and highly error-prone. State-of-the-art heuristic-based approaches produce an overwhelming number of false positives, while vanilla Large Language Models (LLMs) provide incomplete suggestions due to their limited context and inability to interact with refactoring tools. This leaves developers with incomplete refactorings or burdens them with filtering too many false positives. Coordinated renaming is exactly the k
📄 Full Content
📸 Image Gallery
