Answers
Answers is Driver’s product for asking code questions about software behavior, implementation, dependencies, and changes. Responses cite the relevant sources, and you can ask follow-up questions in the conversation to explore the details.
Investigations
| Term | Meaning |
|---|---|
| Investigation | A conversation with Driver about a software question or issue, including the evidence, findings, and follow-ups. |
| Automated investigation | Driver’s investigation of a newly created Jira ticket when the project’s Automatic triage switch is on. The findings are posted on the ticket. |
| Private continuation | Your own investigation starting from the automated investigation. Each person continues independently with Driver. |
| Finding | A claim or conclusion supported by source evidence. |
| Evidence | The code, commit, ticket detail, document, or supplied record that supports a finding. |
| Hypothesis | An explanation that fits some evidence but still needs checking. |
| Report | The written findings of a support ticket investigation. Use it to review the evidence and request a draft for a particular audience. |
| Feedback | Your rating of how useful or correct the investigation was. Feedback is separate from closing the Jira ticket. |
Codebase context
| Term | Meaning |
|---|---|
| Codebase | A connected repository that Driver is allowed to read. |
| Basic Codebase Context | Source-file access, file discovery, and code search. |
| Advanced Codebase Context | Basic capabilities plus prepared subsystem maps, file documentation, relationships, change impact, and history. |
| Atlas | The thematic map of a codebase’s subsystems and the files that implement them. |
| MCP | The protocol AI tools use to connect to Driver. The codebase MCP server provides source and prepared context; the investigation MCP App runs investigations and shows evidence inside the AI tool. |
| Driver Investigations MCP App | The early-access App for investigating and reviewing evidence in Claude Cowork or ChatGPT Work. See Local AI Tools for access. |
| CLI | The driver terminal command for investigations, source setup, and administration. |
Management
| Term | Meaning |
|---|---|
| Source | A repository, Jira project, or documentation service that an investigation can read. |
| Machine identity | A service identity with access to particular codebases, used by an agent or integration. |
| Jira project scope | A Jira project connected to Driver and its automatic-investigation settings. |
| Automatic triage | The on/off setting that starts investigations for tickets created after it is enabled. |
| Investigation Metrics | The organization-level view of ticket performance and investigation feedback. |