rtk-ai/rtk

cargo output on success is too terse, making it ambiguous

Open

#759 opened on Mar 21, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallfilter-qualitygood first issue

Description

cargo check returned cargo build (0 crates compiled)

which - to claude - was ambiguous - it didn't know if there were errors or not, so it tried several work-arounds, consuming extra tokens.

as work-arounds, it ran rtk proxy cargo check, and RUSTFLAGS="-D warnings" rtk proxy cargo check

Claude said it expected to see the "Finished dev profile ..." message.

Suggestion: include the 'Finished ...' message in the success output

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Rust knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Examine the command execution module in the codebase, likely in a file like `src/commands.rs` or `src/proxy.rs`. Find where `cargo check` output is captured and printed. Add logic to include the 'Finished' message from cargo's stderr/stdout when the command succeeds. Ensure the change is minimal and does not affect error handling. Consider adding tests for the output format.