rtk-ai/rtk

`rtk init -g` shows redundant "run `rtk init -g`" warning

Open

#1011 opened on Apr 4, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallgood first issue

Description

Description

Running rtk init -g prints a confusing warning before it has a chance to install the hook:

$ rtk init -g
[rtk] /!\ No hook installed — run `rtk init -g` for automatic token savings

The warning tells the user to run the exact command they're already running.

Steps to Reproduce

  1. Uninstall any existing hooks: rtk init -g --uninstall
  2. Reset the rate-limit marker: rm ~/Library/Application\ Support/rtk/.hook_warn_last
  3. Run rtk init -g
  4. Observe the redundant warning before the hook is installed

Root Cause

maybe_warn() in hook_check.rs fires for all commands except Gain before the command dispatches. When the command is Init, the hook hasn't been installed yet, so the check sees a missing hook and warns.

The warning is also rate-limited to once per day, making it hard to reproduce consistently.

Expected Behavior

rtk init -g should not warn missing hooks nor redundantly recommend running rtk init -g again. If anything, it should indicate that it's about to install the hooks.

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Rust knowledgeFamiliarity with CLI argument parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
The issue is in `hook check.rs`, specifically in the `maybe warn()` function that fires for all commands except `Gain` before dispatch. To fix, add a check for the `Init` command so that the warning is skipped when `init` is being run. The rate limiting logic should also be considered to ensure the warning only appears when appropriate.