rtk-ai/rtk

`rtk init` hangs in non-interactive environments (v0.36.0 telemetry consent gate)

Open

#1307 opened on Apr 14, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallgood first issueresolved-pending-close

Description

Description

rtk init -g --hook-only --auto-patch hangs indefinitely in non-interactive environments
(Docker/devcontainer builds, CI) since v0.36.0. The hook setup completes and output is printed, but the process never exits — it blocks waiting for stdin on the telemetry consent prompt.

Reproduction

# In any non-interactive context (Dockerfile, devcontainer postCreateCommand, CI):
rtk init -g --hook-only --auto-patch                                                             
# Process prints hook setup output, then hangs forever

Last visible output before hang:

RTK hook already up to date (hook-only mode).

  Hook: /home/node/.claude/hooks/rtk-rewrite.sh                                                  
  Note: No RTK.md created. Claude won't know about meta commands (gain, discover, proxy).
                                                                                                 
  settings.json: hook already present                                                          
  Restart Claude Code. Test with: git status

Expected behavior

rtk init should detect non-interactive environments (e.g., ! -t 0 / no TTY on stdin) and skip the consent prompt, or respect RTK_TELEMETRY_DISABLED=1 to suppress it entirely.

Actual behavior

The process blocks on stdin waiting for consent input that will never come.
RTK_TELEMETRY_DISABLED=1 does not prevent the prompt — it only disables data collection after consent is given.

Workaround

RTK_TELEMETRY_DISABLED=1 timeout 10 rtk init -g --hook-only --auto-patch 2>/dev/null || true

Environment

  • RTK: v0.36.0 (v0.35.0 worked fine)
  • OS: Debian Trixie (Docker container, node:24-trixie-slim)
  • Arch: ARM64 (Apple Silicon via Docker Desktop)
  • Context: devcontainer postCreateCommand (no TTY)

Contributor guide

Tech stack
rustshelldocker
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 RustTTY detection conceptsenvironment variables
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the telemetry consent prompt implementation in the rtk codebase, likely in `src/telemetry.rs` or where stdin is read. Determine how to detect non interactive environment using Rust's `atty` crate or `std::io::IsTerminal` trait. Consider also respecting `RTK TELEMETRY DISABLED` env var to skip the prompt entirely. Check git history to see what changed between v0.35.0 and v0.36.0 that introduced the regression.