These are agent-facing workflows where fast, trustworthy workspace search matters more than another shell command.
Ask
> Find the user controller - I do not remember the exact file name.
Why Scout helps
Fuzzy search ranks files and identifiers by match quality and frecency, so a rough query like "usrctrl" lands on the right file without spelling it exactly.
Tools: find
Ask
> Find every occurrence of the deprecated config key, exhaustively - I need all of them.
Why Scout helps
Strict modes are exhaustive with deterministic order and an explicit exhaustive flag, so the agent can treat the result as complete instead of hoping grep flags were right.
Tools: find
Ask
> Search the workspace for /fn handle_\w+/ and list the matching functions.
Why Scout helps
A /re/ query forces regex; results come back paginated with previews and workspace-relative paths ready for follow-up tools.
Tools: find
Ask
> Find "timeout" as a whole word, but only under src and not in test directories.
Why Scout helps
One scope grammar covers path prefixes, include/exclude globs, and language filters, replacing per-tool shell glob dialects.
Tools: find
Ask
> I just applied the rename - confirm no old spellings remain.
Why Scout helps
Every query flushes pending watcher changes before answering, so the search reflects the edit that just happened without a manual re-index.
Tools: find, sync
Ask
> Which search server should handle this C# question?
Why Scout helps
server_status reports detected sibling servers, and find hints name Glider or TGlider when a hit belongs to their language, so the agent upgrades instead of guessing.
Tools: server_status, find