rtk-ai/rtk

[Feature Request] Support selective command hijacking and additional modern CLI tools (fd, rg, eza)

Open

#1,863 opened on May 13, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:cliarea:configenhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe. Currently, the hijacking mechanism seems to be an "all-or-nothing" approach. While rtk provides great AI enhancements, it sometimes conflicts with other modern CLI tools I use (e.g., using eza as a replacement for ls or grep).

I find that git is the most frequent and safest use case for AI assistance in my workflow. I would like to use rtk specifically for git commands while letting my other specialized tools handle their respective tasks without interference.

Describe the solution you'd like

Selective Hijacking (Whitelist/Blacklist): I would like a configuration option to specify which commands rtk should hijack. For example, a setting like hijack_include: ["git"] or hijack_exclude: ["ls", "grep"].

Support for Modern Tools: I would love to see native support (or optimized wrappers) for the following tools:

fd (modern find)

rg (ripgrep)

eza (modern ls)

Describe alternatives you've considered I have tried manually disabling hijacking, but then I lose the excellent AI integration for git, which is the core of my productivity.

Additional context Allowing users to only hijack git would make the tool much "safer" and less intrusive for users who have highly customized shell environments with existing modern Rust-based CLI tools.

Contributor guide