In my opinion, there is a misunderstanding regarding the ClassCrawler intention to replace codesearch. They’re different.
While codesearch, simply shows the occurrences of the wanted text in multiple repositories, ClassCrawler rather shows and searches for relationships between methods and classes.
For example, this query https://classcrawler.prettyclear.com/?q=%7B%22fullName%22%3A%20%22AbstractCo... not only shows you a method and a place where it occurs, it additionally demonstrates your “overrides/overridden” sections with methods that belong to the same hierarchy.
Furthermore, you can search not only for specific text or symbol, but you can also search for specific relationship: https://classcrawler.prettyclear.com/?q=%7B%22overrides%22%3A+%7B%22%24in%22... demonstrates all methods which override Content::getRedirectTarget.
And not only in core, but it processes extensions as well. Note “ProofreadPage\Page\PageContent::getRedirectTarget()” belongs to an extension.
Basically, ClassCrawler is like your local IDE that works globally like codesearch. So ClassCrawler does not replace Code search, it rather extremely extends its functionality.