rtk-ai/rtk

Config key to auto-allow specific ask-level commands ([hooks] allow_ask_commands)

Open

#1344 opened on Apr 16, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
effort-smallenhancementgood first issue

Description

Summary

Some registry entries (e.g. jest, vitest) return exit code 3 from rtk rewrite, surfacing a permission prompt on every invocation. Users in long agentic sessions (Claude Code, Cursor) get prompted repeatedly for commands they have already decided to trust. The ask/auto-allow decision is currently hardcoded in src/discover/rules.rs — there is no config escape hatch.

The existing [hooks] exclude_commands does the opposite (skip rewrite entirely). Missing: an allowlist for ask-level rules.

Proposed shape

[hooks]
allow_ask_commands = ["jest", "vitest"]

When the rewrite lookup lands on an ask-level rule, check if the command name is in this list and emit permissionDecision: "allow" if so.

Why config vs. per-command PR

Trust levels vary. Putting ask → auto-allow in user config lets individuals opt in without forking or pushing per-command changes upstream. Also scales to future additions without repo churn.

Environment

  • rtk v0.36.0 (Homebrew, macOS)
  • Consumer: Claude Code PreToolUse(Bash) hook installed via rtk init -g

Contributor guide

Tech stack
rust
Domain
clitooling
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Rust basicsTOML config
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue proposes adding a new config key `allow ask commands` to the `[hooks]` section. Implementation likely requires modifying `src/discover/rules.rs` to read this config after loading the TOML file, then during ask level command checking, emit `permissionDecision: "allow"` if the command is in the list. The current logic for ask level rules should be extended. No linked PRs or assignees yet; the single comment may clarify expectations. Testing should cover parsing the new config and behavior changes.