chore(rebrand): complete user-facing vtcode → bvtcode rename #3

Merged

dimgigov merged 2 commits from cursor/rebrand-bvtcode into main 2026-09-19 17:55:52 +00:00

Conversation 0 Commits 2 Files changed 897 +4579 -4561

dimgigov commented 2026-09-19 17:50:19 +00:00

Owner

Copy link

Finish the user-facing rebrand: prose display name "VT Code" → "BVT Code",
CLI invocations vtcode <cmd> → bvtcode <cmd>, and install examples,
across docs, Rust string literals/comments, shell scripts, TS/JSON, and
templates.

Also repairs regressions from the earlier scripted passes:

• keep release asset names as vtcode-<v>-<target> (the self-updater
  matcher requires the vtcode- prefix and upstream only publishes those)
• Homebrew formula class now matches the renamed file (class Bvtcode)
• restore the upstream attribution link in README.md
• fix stale doc anchors and the VS Code extension test id

Intentionally unchanged: Rust crate names, upstream URLs, macOS/Flatpak
bundle id, vtcode: wire-protocol prefixes, tracing targets, keyring
service ids, and CHANGELOG.md.

Co-authored-by: Cursor cursoragent@cursor.com

Pull Request

Description

Please include a summary of the changes and the issue that this PR addresses. Include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue number)

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so others can reproduce. Include any relevant details for your test configuration.

• Rust tests: cargo test
• Linting: cargo clippy
• Formatting: cargo fmt
• Build: cargo build

Test Configuration:

• Rust version:
• Operating system:
• Toolchain:

Checklist:

• My code follows the style guidelines of this project (Rust conventions, naming, etc.)
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes (cargo test)
• I have run cargo clippy and addressed any issues
• I have run cargo fmt to ensure proper formatting
• Any dependent changes have been merged and published in downstream modules
• I have updated the CHANGELOG.md if this change affects the user-facing behavior
• I have checked my code and corrected any misspellings

Additional Context

Add any other context or screenshots about the pull request here.

Finish the user-facing rebrand: prose display name "VT Code" → "BVT Code", CLI invocations `vtcode <cmd>` → `bvtcode <cmd>`, and install examples, across docs, Rust string literals/comments, shell scripts, TS/JSON, and templates. Also repairs regressions from the earlier scripted passes: - keep release asset names as `vtcode-<v>-<target>` (the self-updater matcher requires the `vtcode-` prefix and upstream only publishes those) - Homebrew formula class now matches the renamed file (`class Bvtcode`) - restore the upstream attribution link in README.md - fix stale doc anchors and the VS Code extension test id Intentionally unchanged: Rust crate names, upstream URLs, macOS/Flatpak bundle id, `vtcode:` wire-protocol prefixes, tracing targets, keyring service ids, and CHANGELOG.md. Co-authored-by: Cursor <cursoragent@cursor.com> # Pull Request ## Description Please include a summary of the changes and the issue that this PR addresses. Include relevant motivation and context. List any dependencies that are required for this change. Fixes # (issue number) ## Type of Change Please delete options that are not relevant. - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? Please describe the tests that you ran to verify your changes. Provide instructions so others can reproduce. Include any relevant details for your test configuration. - [ ] Rust tests: `cargo test` - [ ] Linting: `cargo clippy` - [ ] Formatting: `cargo fmt` - [ ] Build: `cargo build` **Test Configuration**: * Rust version: * Operating system: * Toolchain: ## Checklist: - [ ] My code follows the style guidelines of this project (Rust conventions, naming, etc.) - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes (`cargo test`) - [ ] I have run `cargo clippy` and addressed any issues - [ ] I have run `cargo fmt` to ensure proper formatting - [ ] Any dependent changes have been merged and published in downstream modules - [ ] I have updated the `CHANGELOG.md` if this change affects the user-facing behavior - [ ] I have checked my code and corrected any misspellings ## Additional Context Add any other context or screenshots about the pull request here.

dimgigov added 1 commit 2026-09-19 17:50:19 +00:00

chore(rebrand): complete user-facing vtcode → bvtcode rename ... 403af8cb85

Finish the user-facing rebrand: prose display name "VT Code" → "BVT Code",
CLI invocations `vtcode <cmd>` → `bvtcode <cmd>`, and install examples,
across docs, Rust string literals/comments, shell scripts, TS/JSON, and
templates.

Also repairs regressions from the earlier scripted passes:
- keep release asset names as `vtcode-<v>-<target>` (the self-updater
  matcher requires the `vtcode-` prefix and upstream only publishes those)
- Homebrew formula class now matches the renamed file (`class Bvtcode`)
- restore the upstream attribution link in README.md
- fix stale doc anchors and the VS Code extension test id

Intentionally unchanged: Rust crate names, upstream URLs, macOS/Flatpak
bundle id, `vtcode:` wire-protocol prefixes, tracing targets, keyring
service ids, and CHANGELOG.md.

Co-authored-by: Cursor <cursoragent@cursor.com>

dimgigov added 1 commit 2026-09-19 17:54:35 +00:00

Merge remote-tracking branch 'origin/main' into cursor/rebrand-bvtcode-merge ... 2f023641e9

Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	docs/README.md

dimgigov merged commit f5a697feed into main 2026-09-19 17:55:52 +00:00

dimgigov referenced this pull request from a commit 2026-09-19 17:55:52 +00:00

Merge pull request 'chore(rebrand): complete user-facing vtcode → bvtcode rename' (#3) from cursor/rebrand-bvtcode into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

vrcode/vtcode-cli!3

No description provided.