[ax] Never emit ANSI when output is not a TTY, even with --ansi - #8453
Merged
Conversation
This was referenced Sep 4, 2026
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
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.
Why
When output is piped, redirected or captured by an agent, colored output is noise - ANSI escape bytes an agent has to strip. Symfony already drops color on a non-TTY by default, but an explicit
--ansioverrides that detection and forces color even into a pipe:What
Force console decoration off when STDOUT is not a TTY, regardless of
--ansi. Real terminals are unaffected (they keep color); only non-interactive output is guaranteed clean.Same non-TTY detection used for the progress bar in #8444.
Verification
Piping a run with
--ansi(2 changed lines):Plain piped output was already clean (0) and stays 0; interactive terminal output keeps color.
This is env-dependent output plumbing that reads the real STDOUT stream, so it is verified via the CLI before/after rather than a unit test.