What a reader sees
The public CLI overview at /ai/ti-overview/ carries an H2 section titled "TiDB Cloud CLI and Drive9", and Drive9 appears 5 times on that page:
TiDB Cloud CLI and Drive9
The TiDB Cloud CLI installs a bundled Drive9 companion named ti-drive9. The TiDB Cloud CLI owns profile selection, TiDB Cloud credentials, region and Filesystem selection, output formatting, and ti error behavior. The companion owns Filesystem data-plane semantics, FUSE and WebDAV mounts, layers, pack and unpack, Git workspace acceleration, journals, and vault operations. You do not need to install, configure, or invoke Drive9 separately for normal TiDB Cloud CLI workflows.
Why this is worth a decision rather than a quick edit
ti-drive9 is a real binary that ships and lands on the user's machine, so this isn't simply stale text that can be deleted — a reader who lists their install directory will see the name regardless. But right now it's the only place a public reader meets it, and it arrives with no explanation of what Drive9 is or how it relates to the product they came for.
The naming is inconsistent across our public surfaces:
- Product marketing uses TiDB Cloud Filesystem exclusively — the landing page that launched today (https://www.pingcap.com/tidb/tidb-cloud-filesystems/) never mentions Drive9.
- These docs introduce Drive9 as a second named component.
- The last paragraph then tells the reader they don't need to think about it — which raises the question of why it's given a section heading at all.
So a reader arriving from the landing page meets an unexplained second product name at the exact moment they're deciding whether to trust the CLI.
Options
- Keep the binary, drop the branding. Describe it functionally — "the CLI bundles a data-plane companion (
ti-drive9) that handles mounts, layers, journals and vault operations" — and remove Drive9 from the heading. Reader gets the fact without a second brand to learn.
- Keep it and explain it, if Drive9 is meant to be a public name — one line on what it is and how it relates to TiDB Cloud Filesystem.
- Demote it out of an H2 into a note under "What TiDB Cloud CLI manages", since the section's own conclusion is that users don't interact with it.
I'd suggest (1) unless there's a deliberate plan to make Drive9 a public-facing name — in which case it needs a proper introduction, not a passing mention.
Flagging rather than sending a PR because this is a naming call, not a typo. Happy to write whichever version you pick.
/cc whoever owns CLI naming
What a reader sees
The public CLI overview at
/ai/ti-overview/carries an H2 section titled "TiDB Cloud CLI and Drive9", andDrive9appears 5 times on that page:Why this is worth a decision rather than a quick edit
ti-drive9is a real binary that ships and lands on the user's machine, so this isn't simply stale text that can be deleted — a reader who lists their install directory will see the name regardless. But right now it's the only place a public reader meets it, and it arrives with no explanation of what Drive9 is or how it relates to the product they came for.The naming is inconsistent across our public surfaces:
So a reader arriving from the landing page meets an unexplained second product name at the exact moment they're deciding whether to trust the CLI.
Options
ti-drive9) that handles mounts, layers, journals and vault operations" — and removeDrive9from the heading. Reader gets the fact without a second brand to learn.I'd suggest (1) unless there's a deliberate plan to make Drive9 a public-facing name — in which case it needs a proper introduction, not a passing mention.
Flagging rather than sending a PR because this is a naming call, not a typo. Happy to write whichever version you pick.
/cc whoever owns CLI naming