This release adds a new usage tracking dashboard for administrators, along with continued performance and stability improvements.

Usage Tracking

A new usage tracking dashboard gives administrators and team leads detailed breakdowns of how Driver is being used across your organization.

• Total requests. See org-wide Driver activity over time.
• By user. Understand adoption and engagement across individual users.
• By codebase. See how Driver usage is distributed across your repos.
• By service. Break down activity across MCP, chat, and other Driver tools.
• Trends. Track usage patterns over time.

Performance & Stability

Continued improvements to core infrastructure for better reliability as usage grows.

We’ve shipped a number of important updates to static analysis, concurrency strategies, and cloud infrastructure to improve core performance and scaling. This release also introduces Labs and our first Labs feature, Ticket Analysis Integration.

Labs

Labs is a new opt-in feature system that lets users experiment with upcoming capabilities and early beta features directly in the Driver app. Use Labs to control which experimental features are active for your workflow. Ticket Analysis is the first feature available through Labs, with more to come.

Ticket Analysis Integration

An automatic ticket analysis system that connects Driver’s deep codebase context to your issue tracker. Connect Linear or JIRA, and Driver will analyze tickets and provide context-enriched follow-up grounded in your actual code.

Get started: Enable Ticket Analysis in Labs, then connect your Linear or JIRA instance.

Performance Improvements

A ground-up replacement of the symbol table implementation collapses processing jobs that previously ran in sequence, reducing total analysis time significantly.

Infrastructure

Continued improvements to asynchronous orchestration, cloud infrastructure, and autoscaling to provide better reliability and responsiveness. The performance and infrastructure provide important foundation for upcoming features such as multi-branch support.

Coming Soon

Multi-branch support, usage tracking, content registration, and more.

This release adds machine-level authentication for CI/CD systems, two new MCP tools, SCIM 2.0 provisioning, and real-time telemetry for codebase processing.

Machine Access for MCP

A new “Machine” identity type lets automated systems (CI/CD pipelines, scripts, bots) authenticate to the Driver MCP server independently of any user account.

• Survives employee turnover. Machine tokens are tied to your organization, not an individual. If the person who set it up leaves, your pipelines keep working.
• Fine-grained access control. Machines only see the codebases you grant them. Assign a machine to a team or grant access to specific codebases directly.
• Full admin visibility. A new “Machine Access” page in org settings lets admins see all machines, what they can access, when they were last used, and rotate or revoke keys instantly.

Get started: Org admins go to Settings → Machine Access → Create Machine.

New MCP Tools and Documentation

Two new tools and an overhaul of MCP documentation, optimized for AI agents and user onboarding.

• gather_task_context: Encapsulates an entire typical workflow using Driver’s other tools to gather context on a particular topic. This is now the preferred and primary tool. The other tools remain as primitives to be called as needed.
• get_source_file: Fetches raw source files when they are not available locally.
• Overhauled documentation: Tool descriptions and workflow documentation are now optimized for AI agents. Specific CLAUDE.md, CursorRules, or equivalent files should no longer be needed.

Action required: After updating, remove any Driver tool descriptions from your CLAUDE.md or CursorRules files. The MCP server now handles this automatically.

Real-Time Telemetry

A new telemetry status monitor displays codebase processing progress throughout the application in real time.

SCIM 2.0

Automated user and group provisioning from your identity provider. Manage Driver users, roles, and team membership directly from your directory. When users are added, removed, or reassigned, Driver stays in sync automatically.

Coming Soon

Multi-branch support, sub-agents, more integrations, and Driver solutions to common SDLC use cases.

This release makes it easier to get started with Driver and connect your AI coding tools.

Onboarding Checklist

A new guided setup sidebar helps organization admins quickly configure Driver with progress tracking for each step.

MCP Setup Page

A new dedicated page clarifies exactly how to connect Driver to your favorite AI platform (Claude Code, Cursor, VS Code Copilot, and more), including copy-paste configuration.

We’ve expanded Driver’s infrastructure to better support growing teams and larger codebases. This release focuses on processing pipeline optimizations for repositories with hundreds of thousands of files, and context generation now runs in parallel across multiple branches.

This release brings new visibility into your codebases, simplified authentication, and enterprise-ready deployment options.

Introducing Analytics

Get visibility into your repositories’ health and activity with Analytics. See commits, contributors, and code changes over time across your organization.

Organization Dashboard

See aggregate metrics across all your codebases in one view: total commits, unique contributors, active repositories, and trend lines.

Codebase Analytics

Dive deeper into individual repositories with detailed views. Track codebase size over time, yearly activity, and contributor patterns.

Branches & Contributors

Track branch health with status indicators (Default, Active, Stale) and see per-branch metrics. View contributor activity, commit frequency, and collaboration patterns.

Where to find it: Navigate to Settings → Analytics in your organization.

Single-Tenant Deployments

Private single-tenant deployments are now available for organizations requiring dedicated infrastructure.

Simplified MCP Authentication

You no longer need API keys to use Driver’s MCP tools. Authenticate directly with your Driver account for a streamlined setup experience.

We are releasing several updates focused on access control, administration, and deployment readiness.

Role-Based Access Control (RBAC)

Users, teams, and roles are now available in Driver, mirroring your internal organization and access controls. Default visibility of sources (codebases and PDFs) can be set, and granular access to specific sources can be granted to teams as well as directly to individual users.

IdP and SCM Integrations Are Next

The initial RBAC solution is designed to provide everything you need to map your access-control policies to Driver. As next steps, the team will be working on SCIM, SSO (via MS Entra ID), and direct mapping from your source-control management system.

Better Onboarding Flow and Management UX

The team is working to make initial onboarding and ongoing administration much easier. This is another area of active investment.

Streamlined Release Infrastructure

Recent release-infrastructure improvements will enable better scaling and faster updates going forward.

With richer contextual intelligence flowing into Chat, responses are more grounded and context-aware.

Driver Chat now uses the same tools provided by Driver MCP. With richer contextual intelligence flowing into Chat, responses are more grounded and context-aware.

We’ve improved language specialization for Ruby. Ruby moved onto our new language specialization mechanism, yielding improved Ruby docs: better syntax highlighting, more accurate method signatures, and deeper understanding of metaprogramming patterns.

Pagination added to select MCP tools (reliability fix). Some tools now paginate large result sets to prevent overflow edge cases when LLMs invoke them.

The team is working hard on a new RBAC implementation, multi-branch support, and private single tenant deployments.

We’ve now expanded language specialization to include Go, and we now support codebase integration with Azure DevOps.

Precision Autodocs

You can now generate autodocs for any folder or file you choose. With a single prompt, create concise, structured documentation exactly where you need it.

Deep Context Docs for Every Codebase

Foundational deep context docs are now available in the new Autodocs tab:

• Architecture Guides – detail the structure of your codebases.
• LLM Onboarding Guides – orient agents to key components, their relationships, and navigation paths.
• Development History Guides – built from commit logs to explain the evolution of your codebases.

Performance and Scalability Improvements

You should notice faster and better results across especially large, complex codebases, such as monorepos and polyglot repositories.

Now any Driver-created pull requests and merge requests will get automatically closed. This change was made based on customer feedback.

We’ve refined our automated commit messages to improve validation compatibility.

We’ve been listening to your feedback! We’re launching new ways to make it faster and easier to get value from Driver with My Sources and My Documents.

My Sources

A dedicated space for all your team’s codebases and PDFs — organized with a faster and smoother tagging and filtering system.

My Documents

Access all your team’s documents and templates in one place. View the latest activity, tag your documents, and find what you need quickly.

Also, loading time in both product spaces is now much, much faster.

Shift Your Productivity into High Gear

• Find what you need instantly with our improved tagging and filtering system
• Switch between workflows seamlessly with dedicated spaces for inputs and outputs
• Stay organized effortlessly with clearer information hierarchies and metadata
• Save valuable time with fewer clicks to access your most-used content