#Debug with Context

When debugging, the agent needs to understand how components connect. Driver gives it the full system map, so it can trace errors across module boundaries instead of searching blindly.

#Example prompts

• "This error is happening in production: [error message]. Help me find the root cause."
• "Trace the request flow from /api/orders to the database."
• "What modules depend on AuthService?"
• "Why would a change in payments/ cause failures in notifications/?"

#What happens

The agent combines multiple Driver tools:

1. get_architecture_overview: Loads system boundaries and component relationships so the agent understands how data flows between modules.
2. get_code_map: Identifies which files and directories are involved in the affected area. The agent traces dependencies across the tree.
3. get_file_documentation: Inspects specific functions, error handling paths, and interfaces in the files along the execution path.

The agent follows the error from the symptom to the source, using the architecture map to cross module boundaries correctly. It identifies not just where the error occurs, but why the system reached that state.