Who it is forA developer in Aside who needs to locate every file that mentions a term, such as TODO, across a large local folder.
The problemDoing this natively means many separate reads and bash calls, and every matched file's content can flood the model context.
The outcomeThe agent gets the list of matching paths in one call, with the file contents kept out of the context.
What you need first
- Node.js 18 or newer
- Aside installed with its daemon running on macOS or Windows
- ripgrep on the PATH for the CLI route (the MCP route uses Aside's bundled ripgrep automatically)
- Browsing turned on in Aside for the browser batch use case
Steps
- Run
npm install -g aside-codemode - Run
codemode --install-mcp - Run
codemode --doctorand confirm the state reads activated - Start a new Aside session so the mcp__aside-codemode__execute_code tool is attached
- Ask the agent to run a search over the project folder and return only the paths
Prompt for your agent
Use the aside-codemode execute_code tool to search <project folder> for the text <term> with the search content action, and return the unique file paths only. Verify that the result contains paths and no file bodies.
Caveat. The 55s to 1s folder comparison is an operator report that the README says was not independently reproduced, so measure your own folder before relying on the number.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page