Skip to content

🎨 Palette: Route logs to stderr, keeping data on stdout#175

Merged
ffalcinelli merged 1 commit into
mainfrom
jules-5503033966193379511-eb717caa
Jul 26, 2026
Merged

🎨 Palette: Route logs to stderr, keeping data on stdout#175
ffalcinelli merged 1 commit into
mainfrom
jules-5503033966193379511-eb717caa

Conversation

@ffalcinelli

Copy link
Copy Markdown
Owner

πŸ’‘ What: Changed all instances of UI logs/prompts across the project to output to stderr (using eprintln! instead of println!), specifically targeting standard logs (info, error, success, warn) in src/utils/ui.rs and across all action scripts.
Crucially, the diff outputs inside plan logic (like print_diff) remain on stdout.
🎯 Why: Standard Unix philosophy dictates that informational/interactive logs should go to stderr, while the actual output payload goes to stdout. This allows users to safely pipe kaji commands (e.g. kaji plan > changes.patch) without UI loading indicators, checkmarks, or warnings polluting the redirected file.
πŸ“Έ Before/After:
Before:

$ kaji plan > patch
# The patch file now contains "βœ… No changes planned" and diff headers.

After:

$ kaji plan > patch
βœ… No changes planned # Prints to terminal correctly
# The patch file is perfectly clean or empty

β™Ώ Ergonomics: Vastly improves scripting, composition, and log redirection.


PR created automatically by Jules for task 5503033966193379511 started by @ffalcinelli

Co-authored-by: ffalcinelli <1167082+ffalcinelli@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@codecov

codecov Bot commented Jul 25, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 97.87234% with 1 line in your changes missing coverage. Please review.
βœ… Project coverage is 96.13%. Comparing base (35371f9) to head (c707558).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/inspect.rs 80.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   96.10%   96.13%   +0.03%     
==========================================
  Files          29       29              
  Lines        2898     2926      +28     
==========================================
+ Hits         2785     2813      +28     
  Misses        113      113              

β˜” View full report in Codecov by Harness.
πŸ“’ Have feedback on the report? Share it here.

πŸš€ New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ffalcinelli
ffalcinelli merged commit 1657529 into main Jul 26, 2026
10 checks passed
@ffalcinelli
ffalcinelli deleted the jules-5503033966193379511-eb717caa branch July 26, 2026 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant