Aider codebase context without rereading the repository

What is Aider codebase context?

Aider codebase context is the set of files, repository-map information, Git history, conventions, and model messages Aider uses during a coding session. The context window is finite, so choosing the right structural information matters as much as the model's raw coding ability. A persistent graph helps the assistant decide which files and relationships belong in the active working set. The useful unit is a bounded relationship answer that makes the next source read more targeted.

• Aider's repository map highlights code relationships for the active model.
• Selected files provide full implementation detail.
• Git history explains recent changes but not every architectural boundary.
• Graphify adds persistent structure beyond the active chat.
• Use the graph to choose the smallest useful set of files for the task.

How is Graphify different from Aider's repository map?

Aider's repository map is generated dynamically to fit the current task and token budget. Graphify is a persistent project artifact that captures explicit relationships, confidence labels, communities, and documentation links for repeated queries and human review. Neither map proves runtime behavior; their value is in reducing discovery cost before source and tests are examined.

• Aider's map is optimized for immediate model context.
• Graphify's graph is optimized for deterministic navigation and reuse.
• Aider reads selected code; Graphify reveals paths between code and docs.
• The strongest workflow uses both and verifies both against source.
• Treat Aider's map as live context selection and Graphify as durable project memory.

How do you install Graphify for Aider?

Run graphify aider install after installing graphifyy. The installer writes a Graphify section to AGENTS.md, where Aider can find project-specific commands, graph paths, and rules for querying before broad repository reads. The installer is not a replacement for the graph build, and it does not ask Aider to ignore its own repository map.

• Install Python 3.10 or newer and graphifyy.
• Run graphify aider install from the repository root.
• Keep the AGENTS.md section concise and repository-specific.
• Run graphify extract . to produce graphify-out artifacts.
• Re-run the installer after upgrading Graphify when command guidance changes.

How should Aider query dependencies and call paths?

Ask for the smallest structural answer that supports the task: callers, affected nodes, a path between two symbols, or a community summary. Then add the relevant source files to Aider so the model can reason from exact code instead of graph summaries alone. Bounded queries protect the context window and produce a clearer audit trail than asking for the whole project. If a result is surprising, inspect the graph edge in source before adding more files.

• Use graphify affected for reverse dependency and blast-radius questions.
• Use graphify path to understand how two modules connect.
• Use graphify explain for a bounded neighborhood around one symbol.
• Add verified source files to the Aider chat before editing.
• Ask for a budgeted query when the graph neighborhood is large.
• Remove graph context that no longer corresponds to the selected working files.
• Keep the graph query and its source verification in the same task transcript.
• Before editing, confirm the returned symbol names still exist in the current checkout.

What belongs in AGENTS.md for Aider?

AGENTS.md should contain working rules rather than a copy of the graph. List the real validation commands, protected paths, graph artifacts, refresh procedure, and the requirement to verify graph-derived claims before changing code. The goal is a short operating contract that remains stable when individual files move.

• Document build, test, type-check, and migration commands.
• State when Aider should query graph.json before searching.
• Reference GRAPH_REPORT.md as the short architecture briefing.
• Require source and test verification for inferred edges.
• Forbid edits based only on a graph summary when the source has not been opened.

How do you keep large-repository context fresh?

Refresh after interface changes, module moves, dependency upgrades, or generated-code changes. Use update mode for code-only structure and a full extraction when docs, PDFs, diagrams, or other semantic inputs changed; then confirm the graph matches the current commit. In long-running branches, rebuild after merges that change interfaces instead of trusting the graph from the branch point.

• Run graphify update after structural code changes.
• Refresh semantic context after important documents change.
• Use .graphifyignore to exclude generated and sensitive files.
• Keep the previous graph available while validating large refactors.
• Record the source revision used to generate the graph.