CODING AGENT WORKFLOW · PRACTICAL GUIDE

Code Navigation Without a Vector Database

Quickly rank likely source files by task words in filenames, paths, and short excerpts before opening full files.

THE PROBLEM

Large repositories make repeated broad file dumps expensive. The MCP tool should narrow where an agent looks without pretending that a short index covers every code relationship.

HOW THIS TOOL WORKS

code_navigate walks a bounded number of entries, skips hidden folders and common build/dependency outputs, and scores source-like files for task terms. Results contain relative paths and a small excerpt so the agent can choose what to read next.

TRY IT

node dist/cli.js navigate --root . --query "find the browser approval gate"

LIMITS

This is a bounded filename/excerpt scan, not a complete semantic index. It does not follow symlinks or parse imports. Build-generated output is skipped on purpose; adjust the source for unusual repository layouts.