rtk-ai/rtk
Vedi su GitHubFeature request: configurable default flags for `rtk read` and `rtk grep`
Open
#2091 aperta il 25 mag 2026
area:configenhancementhelp wantedpriority:medium
Metriche repository
- Star
- (48.085 star)
- Metriche merge PR
- (Merge medio 11g 1h) (45 PR mergiate in 30 g)
Descrizione
Problem
When using RTK with an AI assistant (Claude Code), the flags -l aggressive
(for rtk read) and --ultra-compact (for rtk grep) dramatically improve
token savings — but they must be specified manually on every call.
Measured impact over real sessions:
rtk readwithout flag: ~1-6% savings (101 calls wasted)rtk read -l aggressive: ~80% savingsrtk grepwithout flag: ~50% savingsrtk grep --ultra-compact: ~80% savings
Because these flags cannot be set as defaults, savings depend entirely on the AI assistant's behavior — which is inconsistent across sessions due to context resets. Average adoption sits at ~55% despite explicit instructions in CLAUDE.md.
Proposed Solution
Add a [defaults] section to config.toml allowing users to set default
flags per command:
[defaults]
read_level = "aggressive" # equivalent to -l aggressive on every rtk read
grep_ultra_compact = true # equivalent to -u on every rtk grep