docs: clarify rtk name collision and fix installation confusion#48
Merged
pszymkowiak merged 1 commit intortk-ai:masterfrom Feb 2, 2026
Merged
Conversation
## Problem Users are accidentally installing the wrong "rtk" package: - Rust Type Kit (reachingforthejack/rtk) - type generation tool - Rust Token Killer (rtk-ai/rtk) - LLM token optimizer This causes confusion when `rtk gain` doesn't exist after installation. ## Changes ### Documentation Updates - **README.md**: Add prominent warning about name collision at top - **README.md**: Fix installation instructions with mandatory verification - **CLAUDE.md**: Add name collision warning with verification steps - **INSTALL.md**: Clarify pre-installation checks and wrong package handling ### New Files - **docs/TROUBLESHOOTING.md**: Comprehensive troubleshooting guide covering: - Wrong rtk installed (Type Kit vs Token Killer) - cargo install rtk pitfalls - Missing commands (vitest, pnpm, etc.) - PATH issues and compilation errors - **scripts/check-installation.sh**: Automated diagnostic script that verifies: - RTK installed and in PATH - Correct version (Token Killer with `rtk gain`) - Available features - Claude Code integration status - Auto-rewrite hook configuration ## Verification After these changes, users can quickly diagnose installation issues: ```bash bash scripts/check-installation.sh ``` Fixes installation confusion reported by multiple users. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR addresses user confusion caused by a name collision between two different "rtk" packages on crates.io: the Rust Token Killer (this project) and Rust Type Kit (a different project). The PR adds comprehensive documentation and diagnostic tooling to help users identify and fix installation issues.
Changes:
- Added prominent warning sections across all documentation explaining the name collision
- Created comprehensive troubleshooting guide covering common installation and configuration issues
- Added automated diagnostic script to verify correct installation and detect common problems
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| scripts/check-installation.sh | New automated diagnostic script that verifies correct RTK installation, detects Type Kit vs Token Killer, checks available features, and validates Claude Code integration |
| docs/TROUBLESHOOTING.md | New comprehensive troubleshooting guide covering wrong package installation, missing commands, PATH issues, compilation errors, and Claude Code integration problems |
| README.md | Added name collision warning section at top, enhanced installation instructions with mandatory verification steps, added link to troubleshooting guide |
| INSTALL.md | Added name collision warning, enhanced pre-installation checks to detect wrong package, clarified cargo install rtk pitfalls, added uninstall/reinstall instructions |
| CLAUDE.md | Added name collision warning with verification steps to help AI assistants understand the correct rtk package |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ahundt
pushed a commit
to ahundt/rtk
that referenced
this pull request
Feb 23, 2026
…sion-confusion docs: clarify rtk name collision and fix installation confusion
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Users are accidentally installing the wrong "rtk" package due to a name collision:
This causes significant confusion when users run
cargo install rtkand then find thatrtk gain(the token savings analytics command) doesn't exist. Multiple users have reported this issue.Solution
This PR adds clear warnings and verification steps throughout the documentation to prevent and diagnose this issue.
Documentation Updates
README.md
rtk gainCLAUDE.md
INSTALL.md
cargo install rtkambiguityNew Files
docs/TROUBLESHOOTING.md
Comprehensive troubleshooting guide covering:
cargo install rtkpitfalls and solutionsscripts/check-installation.sh
Automated diagnostic script that verifies:
rtk gaincommand)Users can run
bash scripts/check-installation.shfor instant diagnosis.Testing
The diagnostic script has been tested with:
Impact
This PR will:
rtk gainverification stepsFiles Changed
Total: 5 files changed, 605 insertions(+), 31 deletions(-)
This addresses confusion reported by users who installed
reachingforthejack/rtkthinking it was the token optimizer.🤖 Generated with Claude Code