Skip to content

Investigations

Driver in your tools

Use Jira for the ticket, Driver for an investigation conversation, and your coding tools for the implementation. The CLI and MCP make Driver available to terminal-based and local AI workflows.

ToolWhat it supports
JiraRead automated findings on a ticket and open Continue investigation in Driver to explore further.
Driver web appStart investigations, ask follow-ups, review evidence, and request report drafts.
Driver Investigations MCP AppRun investigations and review evidence in Claude Cowork or ChatGPT Work. Contact Driver support for early access.
Driver CLIStart and continue investigations, read reports, request drafts, give feedback, and manage source setup.
MCP client or editorSearch connected source and, with Advanced Codebase Context, use the prepared maps, relationships, impact, history, and context agent.

Continue in the tool that fits the work

A support engineer can open Driver from Jira, ask for the code behind a symptom, and copy an engineering handoff into the ticket. An engineer can then use Driver’s codebase context in an editor to inspect dependencies and plan the change.

Use the investigation MCP App to work with Driver directly inside a connected AI tool. For an assistant with terminal access, use the CLI investigation commands. The assistant can also connect to the codebase MCP server when it needs source context for coding. See Local AI Tools for early access and setup.