rtk-ai/rtk

[Feature]: reduce the full path for token efficiency

Open

#639 opened on Mar 16, 2026

View on GitHub
 (1 comment) (2 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clieffort-mediumenhancementfilter-qualityhelp wantedpriority:low

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

When I run

cd /Volumes/vol1/Users/user/git/mysuperapp/app
rtk basedpyright --venvpath .venv --pythonversion 3.13 .

I still get logs containing repetitive information, with the full file path, for example:

/Volumes/vol1/Users/user/git/mysuperapp/app/db/database.py
  /Volumes/vol1/Users/user/git/mysuperapp/app/db/database.py:39:5 - warning: Result of call expression is of type "Token[Session | None]" and is not used; assign to variable "_" if this is intentional (reportUnusedCallResult)
  /Volumes/vol1/Users/user/git/mysuperapp/app/db/database.py:43:9 - warning: Result of call expression is of type "Token[Session | None]" and is not used; assign to variable "_" if this is intentional (reportUnusedCallResult)

/Volumes/vol1/Users/user/git/mysuperapp/app is repeated 3 times unnecessarily, while it could be safely replaced with ./ relative to my current folder. I'd like to replace all the file paths with the ./ when I execute rtk in /Volumes/vol1/Users/user/git/mysuperapp/app.

When I execute it from the / root, I can still mention the full path only once and then only refer to that path.

Contributor guide

Research direction
Inspect the codebase for where file paths are printed in diagnostic output, likely in the output formatting or logging module. Implement logic to replace the full path with a relative path from the current working directory, possibly using std::path::Path::strip prefix or similar. Ensure that when the current directory is the root, full paths are still shown once.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCLI development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65