FORCE_COLOR environment variable standard proposed to override NO_COLOR and force ANSI color output

The FORCE_COLOR environment variable is an informal standard designed to address a long-standing friction point in command-line workflows. Many programs disable ANSI color output when they detect non-interactive use, such as piping to another process or redirecting to a file. While NO_COLOR provides a way to suppress colors globally, there has been no consistent way to do the opposite, force colors on, until now. FORCE_COLOR fills this gap by offering a single variable that, when present, instructs supporting software to enable color regardless of context.

Adoption of FORCE_COLOR is voluntary and decentralized. The standard does not require any central registry or approval process; projects can implement it by checking for the environment variable and overriding their default color logic. This simplicity lowers the barrier to entry but also means that support varies across tools. Major runtimes like Node, Python, and Deno already honor FORCE_COLOR, as do popular libraries such as chalk, rich, and pytest. However, older or less actively maintained tools may never add support, leaving gaps in workflows that rely on consistent color output.

The practical cost of adopting FORCE_COLOR is minimal for both users and maintainers. For users, enabling it is as simple as setting an environment variable, which can be done globally or per-session. For maintainers, the change typically involves adding a few lines of code to check for FORCE_COLOR and override the color logic if the variable is present. The example implementation provided in the standard shows this can be done in under ten lines of C. However, the standard does not address edge cases like conflicting flags (e.g., --no-color) or nested environments where both NO_COLOR and FORCE_COLOR are set, leaving those decisions to individual projects.

Where FORCE_COLOR stops working is in tools that do not implement it. Since the standard is informal and opt-in, there is no guarantee that every CLI program will support it. Users may still need to rely on tool-specific flags like --color or -c in some cases, which undermines the goal of consistency. Additionally, FORCE_COLOR does not solve deeper issues like color contrast in different terminal themes or accessibility concerns for users with color vision deficiencies. It is a pragmatic solution for a specific problem, retaining color in logs and output streams, but it does not replace the need for more comprehensive terminal output standards.