It does not route every search through Everything:
- Exact paths stay on direct path checks.
- Project-local filename/content searches stay on ripgrep.
- Unknown or cross-drive indexed searches use es.exe.
- Results are capped at 20 by default, then refined.
In a controlled synthetic test, the 20-result cap reduced returned text by 90% compared with an uncapped 200-result command. That saving came from the cap, not from ES alone; a known-root capped scan was faster.
Repository and 45-second demo:
https://github.com/DerrickZeng33/find-f ... ything-cli
Install:
Code: Select all
npx skills add DerrickZeng33/find-files-with-everything-cli --skill find-files-with-everything -gI'd appreciate feedback from experienced Everything/ES users, especially on the routing rules and CLI syntax.