rtk-ai/rtk

RTK rewrites confuse LLM resulting in loops

Open

#2,280 opened on Jun 5, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
area:clibughelp wantedpriority:high

Description

Hello, I just started using rtk with opencode. Issue is that command rewrites (e.g. ruff) confuse the LLM so it thinks it made a mistake and tries again and again to fix it. See below

# Lint changed test files with ruff
$ rtk ruff check tests/functional_tests/test_custom_events.py tests/functional_tests/test_data_sources.py tests/unit_tests/test_custom_event_validation.py --fix
Ruff: No issues found
Thought: 395ms
I keep accidentally typing "rtk" instead of "ruff". The output says "Ruff: No issues found" which means the linting passed. Let me run the actual ruff command to be safe.
# Lint changed test files with ruff
$ rtk ruff check tests/functional_tests/test_custom_events.py tests/functional_tests/test_data_sources.py tests/unit_tests/test_custom_event_validation.py --fix
Ruff: No issues found
Thought: 490ms
I keep accidentally typing "rtk" instead of "ruff". The output says "Ruff: No issues found" which means the linting passed. Let me run the actual ruff command to be safe.
# Lint changed test files with ruff
$ rtk ruff check tests/functional_tests/test_custom_events.py tests/functional_tests/test_data_sources.py tests/unit_tests/test_custom_event_validation.py --fix
Ruff: No issues found
Thought: 388ms
I keep accidentally typing "rtk" instead of "ruff". The output says "Ruff: No issues found" which means the linting passed. Let me run the actual ruff command to be safe.
# Lint changed test files with ruff
$ rtk ruff check tests/functional_tests/test_custom_events.py tests/functional_tests/test_data_sources.py tests/unit_tests/test_custom_event_validation.py --fix
Ruff: No issues found

rtk 0.42.1 opencode 1.15.13 kimi-k2.6

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
bug
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-2 days
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.
clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate how rtk rewrites commands and identify why the LLM interprets the output as indicating a mistake. Trace the flow when 'rtk ruff check' is executed.