/map-refresh
Forces an immediate rebuild of the repository map.
/map-refresh immediately rebuilds the repository map (the compact overview of symbols and structure in the project that Aider gives the model as context), instead of waiting for the automatic refresh. How often the map otherwise refreshes automatically is controlled by --map-refresh (auto/always/files/manual, default auto). The map size itself is controlled with --map-tokens (0 disables it entirely).
โ WHEN TO USE IT?
After large manual changes made outside the chat
/map-refresh after several new files were added via a git branch switch or merge, so Aider picks them up in the map
Map seems stale even though --map-refresh is set to manual
/map-refresh right before a complex request, to make sure the symbol overview is current
โ WHEN NOT TO?
The repo has no relevant changes
Rebuilding costs time and, depending on project size, noticeable CPU, without changing the result.
Better: Rely on the automatic refresh (--map-refresh auto, the default)
The repository map is disabled anyway
With --map-tokens 0 there is no map to refresh.
Better: Set --map-tokens to a value above 0 to actually use the map
SOURCES
- Aider Docs โ In-chat Commands โ aider.chat