Who it is forA developer or writer in Aside who wants an inventory of files of one type, such as every Markdown note, from a large folder.
The problemBuilding the list with find through bash is slower on large trees, and the agent has to parse noisy output.
The outcomeThe agent gets the matching paths as a clean list, returned in the same call.
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 - Ask the agent to use the file search actions in execute_code to list paths matching the pattern you want (inferred, check the README)
Prompt for your agent
Use the aside-codemode execute_code tool to list every file matching <pattern> under <root folder> and return the paths. Verify the path count against a find run on a small subfolder.
Caveat. The README's listing timing is from one tree of 39,831 paths, and the exact file-name action is not named in the README, so confirm the action name with --doctor or the tool description first.
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