rtk-ai/rtk

rtk grep doesn't work with piped input

Open

#1,476 创建于 2026年4月23日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Rust (48,085 star) (2,914 fork)batch import
bugeffort-smallfilter-qualitygood first issue

描述

Sometimes an LLM wants to pipe a command's output through grep. This doesn't work currently

Steps to reproduce

ps aux | rtk grep bash

Expected result

rtk grep should grep STDIN

Actual result

rtk grep searches through all files in the current working directory for the string

Example

$ ps aux | grep bash
user      215328  0.0  0.0  35152 19720 pts/0    SNs  11:18   0:00 /bin/bash
root      217325  0.0  0.0  24652  9180 pts/1    SN+  11:22   0:00 -bash
user      218879  0.0  0.0  34552 19160 pts/2    SNs  11:23   0:00 /bin/bash
user      224916  0.0  0.0  18980  2364 pts/2    SN+  11:32   0:00 grep --color=auto bash
$ ps aux | rtk grep bash
0 matches for 'bash'

贡献者指南

技术栈
rust
领域
cli
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic RustUnderstanding of stdin
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
80
研究方向
The issue is that `rtk grep` currently only searches files in the current directory and ignores stdin. To fix this, examine the grep command implementation in the rtk codebase (likely in a file handling grep logic). The fix should check if stdin is available (e.g., via `atty::isnt` or similar) and if so, read from stdin instead of falling back to file search. Look for existing Rust crates like `atty` or `std::io::stdin` to detect piped input. The comment on the issue may provide additional context.