Default installation is too invasive

I tried infigraph for over 2 weeks. Initially, I liked it, but I completely uninstalled it as the gains were not worth the effort.

The default installation is too invasive for my local Claude setup.

1. It creates several hooks that run on their own
2. It created autogenerated CLAUDE.MD files
3. It constantly opens/closes/records search sessions

My original use for infinigraph was to find something better than grep/sed/awk/lsp and also save potentially on tokens. But it turned out to be the exact opposite. On some of my sessions, 30% of usage was just on Infigraph

I understand what you are trying to do, but at this point in time I believe a simpler installation mode is needed.

1. The simplest mode would be just the mcp server and nothing else. I would like to call it manually and use the killer feature of finding the blast radius of a change.
2. Then the second mode, where things are mostly automated for indexing and searching
3. Then a more complex mode where you record sessions, extract statistics, etc.

People should be able to choose mode upon installation.

Right now I cannot use infigraph because it tries to do too much and makes the experience even worse.

No files, tests, or code entry points are named in the issue. Start by locating the installation flow and the setup for hooks, autogenerated CLAUDE.MD files, search sessions, and the MCP server; define how the three installation modes differ and verify that the simplest mode enables only the manually invoked MCP server.

Written by the indexing model from the issue text.