rtk-ai/rtk
View on GitHubgradle.toml matcher does not match real `rtk ./gradlew` / `rtk gradle` invocations
Open
#1177 opened on Apr 10, 2026
bugeffort-smallfilter-qualitygood first issue
Description
src/filters/gradle.toml currently has a match_command that does not match the command string RTK actually looks up at runtime, so Gradle output falls back to passthrough.
MWE
# in any Gradle project with ./gradlew present
RTK_TOML_DEBUG=1 rtk ./gradlew tasks
# actual:
# [rtk:toml] looking up filter for: "gradlew tasks" (58 filters loaded)
# [rtk:toml] no filter matched — passthrough
Expected
[rtk:toml] matched filter: 'gradle'
Debug
RTK_TOML_DEBUG=1 rtk ./gradlew tasks
RTK_TOML_DEBUG=1 rtk gradle tasks # if a gradle executable is on the path
Local workaround Use a user/project filter override with:
match_command = "^(?:\\./)?gradlew?\\b"
Proposed fix in rtk
- Update
src/filters/gradle.tomlmatcher to match the normalized lookup string. - Add inline tests for
gradlew ...and./gradlew .... - Add an integration test covering actual fallback lookup behavior.
Context
- Similar fix was already proposed in PR #966, but it was closed unmerged.
- Related: #1178.