The driver command runs investigation conversations and manages Driver from your terminal. Local AI tools can use the same commands to ask questions, read reports, and supply codebase context for implementation work.
Install and sign in
Install on macOS or Linux; on Windows, use WSL:
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/driver-ai/cli/releases/latest/download/driver-installer.sh | shOpen Settings > Access Tokens > Personal in Driver to create a personal access token. Run driver auth login and follow the instructions to sign in with that token.
Run driver auth status to check the selected profile and driver status to review setup. Scripts can use DRIVER_TOKEN and DRIVER_API_URL instead of an interactive login.
Run an investigation
Investigations must be enabled for your organization.
This sequence starts a Jira ticket investigation. Connect Jira and the relevant codebase first, then replace the example URL with your ticket’s URL.
driver investigate start "Investigate https://example.atlassian.net/browse/SUP-2143. Webhook retries stop after the first failure in the payments codebase."
driver investigate list
driver investigate show <investigation>
driver investigate send <investigation> "Check which retry condition explains the reported failure."
driver investigate report <investigation>start and send take the message as a positional argument and wait for Driver’s reply. Replace <investigation> with the returned identifier before running the follow-up commands. Instead of a message argument, use --file PATH to read the request from a file, or --file - to read stdin.
You can also use Answers through the CLI: pass a code question to start and read the response in the command output or with show. Ticket reports and report-based drafts apply to ticket investigations. The CLI reference describes output formats and cancellation behavior.
Use the result
| Command | Purpose |
|---|---|
driver investigate draft <investigation> engineering-handoff | Request an engineering handoff from your ticket report. Other audiences are internal-note and customer-reply. |
driver investigate rate <investigation> partially-right --comment "The affected version needed correction." | Record feedback after Driver replies. Ratings are right, partially-right, wrong, or unused. |
driver investigate close <investigation> | Close your investigation when the work is complete. |
driver investigate reopen <investigation> | Reopen your closed investigation. Existing reply limits still apply. |
Review the report and draft before copying them into Jira or another destination. Closing an investigation does not resolve its Jira ticket.
The CLI can read an automated investigation with show, but its follow-up, draft, feedback, and close commands operate on your own investigations. Open Continue investigation in Driver on Jira to start a private continuation of an automated report.
Set up and administer
Use driver codebase list to discover codebases, driver integration --help to find code-host setup commands, and driver mcp setup --client cursor to print MCP connection guidance. Member, team, SSO, token, indexing, and usage commands support administration according to your access.
Use --output json for machine-readable results and --help to inspect a command. The CLI reference is generated from the published release and includes the full flags, access requirements, and command-specific notes.