the dependency-graph approach makes sense - and its actually why local CLI tools like Cursor, Copilot, Aider etc struggle with impact analysis. They're context-

the dependency-graph approach makes sense - and its actually why local CLI tools like Cursor, Copilot, Aider etc struggle with impact analysis. They're context-window-constrained by design. Theres no persistent graph tracking what depends on what across repos, config files, call paths, etc. "Just put the whole codebase in context" doesnt really work here. You need something indexed before the LLM even gets involved - infra that already knows the dependency relationships. Local tools are great for "write this function." But "what breaks if I change this migration?" is a totally different beast. Thats not a generation problem - its a graph query that needs server-side indexing to answer properly.