Driver

Navigate with Code Maps

Every file and directory in a Driver-connected codebase has an AI-generated description. Instead of searching with grep or browsing file trees manually, ask the agent to find what you need by intent.

Example prompts

  • "What files handle authentication?"
  • "Show me the structure of the api/ directory"
  • "Where is the payment processing logic?"
  • "What modules are in src/services?"

What happens

The agent calls two Driver tools:

  1. get_code_map: Returns a flat list of files and directories with descriptions. The agent adjusts the directory path and depth to zoom in on the right area. A top-level call shows major components. A deeper call shows individual files within a specific module.
  2. get_file_documentation: Returns symbol-level detail for a specific file: functions, classes, interfaces, and their descriptions.

The agent typically starts broad (top-level code map), identifies the relevant directory, then drills down to specific files and symbols.

Code maps work best after orienting. When the agent already knows the architecture, it navigates to the right directory on the first try instead of scanning the full tree.