Toktoken 0.5.0 exposes 27 tools; rustytokens currently advertises and implements 13 (README.md:99-102). The core analysis/ergonomics gaps are:
index_file
find_callers
find_references
inspect_bundle
inspect_dependencies
inspect_hierarchy
search_cooccurrence
search_similar
Existing operations also have narrower semantics than Toktoken: find_dead reports only file-level no-importer nodes (src/ops.rs:126-143), inspect_blast_radius accepts a file rather than a symbol and returns only file-level reverse dependencies (src/ops.rs:183-200), and stats omits staleness/token-savings data. There are no result limits/filters/detail controls on the search operations.
If rustytokens is intended to be a compatible implementation, add the core tools and align their schemas/semantics. If the smaller scope is intentional, document the compatibility boundary. The convenience/management tools (codebase_detect, help, suggest, projects_list, cache_clear, index_github) can remain out of scope unless full tool parity is required.
Toktoken 0.5.0 exposes 27 tools; rustytokens currently advertises and implements 13 (`README.md:99-102`). The core analysis/ergonomics gaps are:
- `index_file`
- `find_callers`
- `find_references`
- `inspect_bundle`
- `inspect_dependencies`
- `inspect_hierarchy`
- `search_cooccurrence`
- `search_similar`
Existing operations also have narrower semantics than Toktoken: `find_dead` reports only file-level no-importer nodes (`src/ops.rs:126-143`), `inspect_blast_radius` accepts a file rather than a symbol and returns only file-level reverse dependencies (`src/ops.rs:183-200`), and `stats` omits staleness/token-savings data. There are no result limits/filters/detail controls on the search operations.
If rustytokens is intended to be a compatible implementation, add the core tools and align their schemas/semantics. If the smaller scope is intentional, document the compatibility boundary. The convenience/management tools (`codebase_detect`, `help`, `suggest`, `projects_list`, `cache_clear`, `index_github`) can remain out of scope unless full tool parity is required.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Toktoken 0.5.0 exposes 27 tools; rustytokens currently advertises and implements 13 (
README.md:99-102). The core analysis/ergonomics gaps are:index_filefind_callersfind_referencesinspect_bundleinspect_dependenciesinspect_hierarchysearch_cooccurrencesearch_similarExisting operations also have narrower semantics than Toktoken:
find_deadreports only file-level no-importer nodes (src/ops.rs:126-143),inspect_blast_radiusaccepts a file rather than a symbol and returns only file-level reverse dependencies (src/ops.rs:183-200), andstatsomits staleness/token-savings data. There are no result limits/filters/detail controls on the search operations.If rustytokens is intended to be a compatible implementation, add the core tools and align their schemas/semantics. If the smaller scope is intentional, document the compatibility boundary. The convenience/management tools (
codebase_detect,help,suggest,projects_list,cache_clear,index_github) can remain out of scope unless full tool parity is required.Fixed in commit
4338e28.