rtk-ai/rtk

Add support for systemctl, python3, ssh, adb, pgrep, pactl, xrandr, pkill

Open

#1,905 opened on May 16, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedplatform:linuxpriority:medium

Repository metrics

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

Description

Missed commands from rtk discover

Running rtk 0.40.0 on Linux Mint 22 XFCE. Hook (PreToolUse → rtk hook claude) is active and intercepting correctly — rtk gain shows 87% savings on covered commands. rtk discover flags these high-frequency commands as still unhandled over 30 days / 197 sessions / 3583 Bash calls:

Command Count (30d) Example
systemctl 122 systemctl --user restart voz-daemon.service
python3 114 python3 /home/techsphere/scripts/clima_full.py --tv
ssh 59 ssh -o ConnectTimeout=4 -o BatchMode=yes ...
adb shell 54 adb shell getprop service.adb.tcp.port
pgrep 48 pgrep -af scrcpy
pactl list 37 pactl list short sinks
xrandr 30 DISPLAY=:0 xrandr --listmonitors
pkill 24 pkill -f "scrcpy.*serial"
crontab 20 crontab -l
pactl info 12 pactl info

Context: Linux automation workspace — TV control (LG WebOS), PipeWire audio routing, voice daemon (Vosk STT), scrcpy bridge to Galaxy A02. Output of systemctl status, pactl list, xrandr --listmonitors, adb shell getprop is verbose and would benefit most.

Priority guess: systemctl + python3 + pactl list together would recover ~50% of the unhandled volume.

Happy to test pre-release builds.

Contributor guide

Research direction
Examine the existing command handlers in the source code (likely in a module like `handlers/`) to understand the pattern for adding new commands. Then implement support for one or two of the listed commands (e.g., `systemctl` and `python3`) by following that pattern, ensuring output is captured and formatted correctly for the rtk hook.
Tech stack
rust
Domain
clidevops
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65