Use Driver Investigations for support tickets and Answers for questions about your code. Both explain their findings with evidence tied to the source.
Support ticket investigations
Driver follows the customer’s report into the code and connected sources that could explain the behavior.
| What to review | How to use it |
|---|---|
| Finding or likely cause | Check whether the explanation accounts for the symptom and environment. |
| Evidence | Open the cited code, commits, ticket details, documents, or data. Distinguish observations from assumptions. |
| Uncertainty | Identify competing causes and the information needed to choose between them. |
| Next step | Ask for a reproduction, check a condition, apply a supported workaround, or prepare an engineering task. |
| Draft | Request an internal note, engineering handoff, or customer reply from your investigation report, then review and copy it to the destination. |
Investigate a ticket explains the Jira entry points. Continue in your private conversation to add evidence or test another explanation.
Answers
Answers explains how your software works, locates implementations, and helps you assess changes, with citations to the relevant code.
Ask a code question
Open Investigations or use the CLI, then name the codebase and what you want to understand. For example: “How do webhook retries work in the payments codebase? Cite the retry condition and tests.”
Answers can read and search connected source with Basic Codebase Context. Advanced Codebase Context adds prepared subsystem maps, relationships, change impact, and history to help trace behavior across the system.
Five useful question formats
| Format | Question | What to ask Driver to explain |
|---|---|---|
| Explain | How does X work? | Follow the flow through the relevant code and cite each important step. |
| Locate | Where is X implemented? | Identify files, symbols, callers, and ownership evidence where available. |
| Compare | Compare implementation options | Compare the implementation work, dependencies, risks, and affected behavior. |
| Impact | What could change if we modify X? | Trace dependents and identify tests or checks for the change. |
| History | Why did X change? | Connect the current behavior to commits and relevant ticket or decision context. |
Ask for a diagram, table, or timeline when it would clarify the answer. Review the underlying source citations and follow up on any missing evidence; the presentation alone does not establish that a claim is correct.