Skip to main content

July 10, 2025: Chat in Driver Docs, Specialization Improvements, and Much More

Updated over 2 months ago

It may be summer, but there’s no slowing down here at the Driver HQ. Here’s what’s new in the Driver platform this week:

Chat in Driver Docs is Here!

First, a big one: We’re excited to introduce you to Chat in Driver Docs. Now you can ask questions about any codebase Driver has documented, whether connected through your VCS provider or uploaded as a file. Chat maintains context as you navigate through your codebase, remembering what you're working on as you view different files, folders, and code elements. Ask simple, open-ended questions or sophisticated prompts with specific format requirements. Some great examples include:

  • Questions about function behavior, dependencies, and structural patterns.

  • Asking for a specific diagram, code example, table, or any output format type.

  • Questions about source code to help you or your team onboard onto a codebase significantly faster.

  • Asking for technical guidance for extending or troubleshooting legacy code.

  • High-level questions about the codebase and its functionality, enabling less-technical or newer team members to get up to speed faster.

Chat also allows you to discuss multiple codebases within a single conversation, making it easy to compare approaches and reuse solutions across different projects. No setup needed—Chat will greet you the next time you open a codebase. We’re eager to hear what you think!


C# Driver Docs Specialization Improvements

This week, we’re also releasing an upgraded version of specialization of C#. Specialization enables richly linked content crossing the file boundary and language-specific optimizations in content and formatting.

Pervasive Source Code Links for Symbols

We’ve added direct links to source code for each symbol in Driver Docs for all specialized languages.


Additional Driver Docs Improvements

We’ve kicked off a Documentation Style initiative, with the goal of delivering crisp, clear language in Driver Docs while keeping all of the platform’s deep technical information and context. We have:

  • Emphasized Standard Technical English (STE) and simple English usage

  • Removed value judgments and speculative language

  • Removed redundant naming and references

  • Prioritized overall conciseness.

This is an ongoing project, with more styling improvements to come.


Other Performance Improvements

You asked, and we delivered: AutoDoc Performance is now significantly faster, with a 10-20% reduction in the time it takes to produce an AutoDoc.

Finally, in Driver Docs, we no longer update parent folder descriptions unless child content changes require it. This avoids trivial and noisy rephrasing for parent folder content upon automatic updates.

Did this answer your question?