rtk-ai/rtk
Vedi su GitHubInconsistent scope defaults: rtk discover (project) vs rtk gain (global)
Open
#1582 aperta il 28 apr 2026
area:clieffort-mediumenhancementhelp wantedpriority:medium
Metriche repository
- Star
- (48.085 star)
- Metriche merge PR
- (Merge medio 11g 1h) (45 PR mergiate in 30 g)
Descrizione
Problem
rtk discover and rtk gain have inconsistent scope defaults AND the --all flag means different things on each:
| Command | Default scope | --all means |
|---|---|---|
rtk discover |
current project | scan all projects |
rtk gain |
global (all projects) | show all time breakdowns (daily + weekly + monthly) |
So --all means "widen scope" on discover but "widen time range" on gain. Running both commands to understand RTK coverage requires opposite flags for scope, and --all is a footgun that does something unexpected on gain.
Expected
- Consistent scope defaults — both should default to global (more useful), with
--projectto narrow - Consistent
--allsemantics — or avoid reusing--allfor unrelated purposes across commands
Suggested fix
rtk discover: default to global, add--projectflag to narrow (matchingrtk gain)- Rename
rtk gain --allto something like--fullor--breakdownto avoid the semantic collision