Answer: Aider's repo map solves the problem that real code is intertwined with and depends on code from many different files, so GPT needs context beyond the code being discussed; sending the entire codebase won't work for even moderately sized repos because they won't fit into the 8k-token context window, and manually picking files or sending whole files is bulky and wastes that window. Status: Confirmed Entry: tool/aider/memory-and-context/code-context-problem Revision: 1 Digest: sha256:ba1b49ccad78478a (changes whenever the content changes) Timeline: Created: 2026-11-13T02:56:14Z Last changed: 2026-11-13T02:56:14Z Last verified: 2026-11-20T11:42:23Z Next check: 2026-11-21T11:42:23Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of context window | 8k-token context window | tokens | [1] | 2026-11-20 problem | Most real code is not pure and self-contained, it is intertwined with and depends on code from many different files in a repo. | | [1] | 2026-11-20 manual approach | manually specify which files to “add to the chat” | | [1] | 2026-11-20 bulky approach | sending whole files is a bulky way to send code context, wasting the precious 8k context window | | [1] | 2026-11-20 Sources: [1] Aider. "aider.chat/docs/ctags.html". https://aider.chat/docs/ctags.html Role: primary. Accessed: 2026-11-20T11:42:23Z Quote: "they won’t fit into the 8k-token context window" (Supports: context window) Quote: "Most real code is not pure and self-contained, it is intertwined with and depends on code from many different files in a repo." (Supports: problem) Quote: "you can manually specify which files to “add to the chat” you are having with GPT" (Supports: manual approach) Quote: "sending whole files is a bulky way to send code context, wasting the precious 8k context window" (Supports: bulky approach) Published: 2026-04-25T16:45:23Z Snapshot SHA-256: abccf8c5ac80c1428b067995fd82eb92e78decd4b04dabff7320f5c99274ae74 (captured 2026-11-13T02:56:14Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T02:56:14Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T11:42:23Z. No independent second source is configured for this entry Last successful check: 2026-11-20T11:42:23Z Last attempt: 2026-11-20T11:42:23Z Notes and limitations: Extracted automatically from a single official source (section "The problem: code context"). Related: https://latestn.com/tool/aider/memory-and-context/ctags-repo-map How does Aider use ctags to build a repo map for code context? https://latestn.com/tool/aider/memory-and-context/include-git-history-context How do I include the git history in the context in Aider? https://latestn.com/tool/aider/memory-and-context/repo-map-context How does Aider use a repository map to provide context to the LLM? https://latestn.com/tool/aider/integrations/connect-lm-studio How do I connect Aider to a model served by LM Studio? https://latestn.com/tool/aider/integrations/disable-git-integration How do I disable git integration in Aider? https://latestn.com/tool/aider/memory-and-context/add-all-files-to-chat How do I add all the files to the chat in Aider? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T02:56:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/aider/memory-and-context/code-context-problem/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/aider/memory-and-context/code-context-problem POST: https://latestn.com/dispute/tool/aider/memory-and-context/code-context-problem with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/aider/memory-and-context/code-context-problem?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What problem does Aider's repo map solve for code context? Revision 1, last verified 2026-11-20T11:42:23Z. https://latestn.com/tool/aider/memory-and-context/code-context-problem (accessed 2026-11-21T09:52:19Z). @misc{LatestN_tool_aider_memory_and_context_code_context_problem_r1, title = {What problem does Aider's repo map solve for code context?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/aider/memory-and-context/code-context-problem}}, note = {Revision 1; digest sha256:ba1b49ccad78478a; last verified 2026-11-20T11:42:23Z; accessed 2026-11-21T09:52:19Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/aider/memory-and-context/code-context-problem