fix: write informational CLI messages to stdout instead of stderr#249
Merged
Conversation
Some terminals render stderr in red, making normal [lore] status messages (agent picker, gateway status, launch info) look like errors. Switch informational messages in run.ts and start.ts from console.error (stderr) to console.log (stdout). Actual errors and shutdown lifecycle messages remain on stderr.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[lore]messages inrun.tsandstart.tsfromconsole.error(stderr) toconsole.log(stdout) so they no longer appear red in terminals that color stderr output.process.stderrtoprocess.stdoutto match the menu stream.All changed messages are printed before the child process is spawned, so there's no risk of interleaving with agent output on stdout.