> ## Documentation Index > Fetch the complete documentation index at: https://docs.graphify.com/llms.txt > Use this file to discover all available pages before exploring further. # Keep the graph current > Refresh changed files, exclude noise, and recover from stale output. Graph queries read the saved graph. Update it after changing the source to keep answers relevant. ## Refresh code ```bash theme={null} graphify update . ``` For an assistant-driven incremental refresh that also considers document context: ```text theme={null} /graphify . --update ``` The code and semantic paths have separate work and caching behavior. A code-only refresh does not replace a semantic refresh for changed documents. ## Watch the project Install the `watch` extra, then: ```bash theme={null} graphify watch . ``` Or install git hooks: ```bash theme={null} graphify hook install graphify hook status ``` The hooks refresh after commits and branch switches. They run in the background, so a query immediately after a commit can briefly see the old graph. After `git pull` or a merge, run `graphify update .` explicitly. ## Exclude unhelpful files Graphify respects ignore files. Add a `.graphifyignore` at the repository root for project-specific exclusions: ```gitignore .graphifyignore theme={null} node_modules/ dist/ coverage/ *.generated.py ``` `graphify extract --no-gitignore` opts out of Git’s ignore rules while retaining `.graphifyignore`. Use it only when ignored source belongs in the graph. ## After a large refactor Graphify has guards against accidentally replacing a graph with a smaller incomplete result. If you intentionally removed substantial source, inspect the warning, then explicitly allow the smaller graph: ```bash theme={null} graphify update . --force ``` Keep a copy of the old graph if you need to compare it. Regenerate visualizations with `graphify export html` after a refresh when necessary.