ESP-IDF build output lost ANSI colors in VS Code integrated terminal (VSC-1820)

[OK1TK]

OS

Windows

Operating System version

Windows 11

Visual Studio Code version

1.107.1

ESP-IDF version

v5.5.2

Python version

3.11.2

Doctor command output

ESP-IDF Extension report (Windows 10, win32 x64 10.0.26200)
VS Code: 1.107.1 (shell: PowerShell)
ESP-IDF Extension: 1.11.0
Workspace: d:\OneDrive\Documents\ESP-IDF\CW_KEYER_20251120_v0.0

ESP-IDF Path: C:<HOMEPATH>\esp\v5.5.2\esp-idf
ESP-IDF version: 5.5.2
Python: 3.11.2
Python venv: C:<HOMEPATH>.espressif\python_env\idf5.5_py3.11_env\Scripts\python.exe
IDF_PYTHON_ENV_PATH: C:<HOMEPATH>.espressif\python_env\idf5.5_py3.11_env
Git: 2.39.2
Port: COM9
Target: esp32s3

ESP-IDF Python requirements: satisfied
Debug adapter requirements: Error
Command used:
python.exe ...\check_python_dependencies.py -r ...\esp_debug_adapter\requirements.txt --constraint ...\espidf.constraints.v5.5.txt

Notable errors in logs:

Repeated ENOENT “Cannot access filePath” for paths under:
C:<HOMEPATH>.vscode\extensions\espressif.esp-idf-extension-1.11.0... (e.g. CMakeLists.txt, sdkconfig)

Build error reported once: “CMake or Ninja executables not found”

esptool errors on multiple COM ports: “PermissionError(13) port busy/denied” and UnicodeEncodeError in cp1252 when printing Czech text (e.g., “Přístup byl odepřen.”)

Extension

No response

Description

After a clean Windows reinstall and fresh ESP-IDF 5.5.2 setup using the official
VS Code ESP-IDF extension, the build output in the VS Code integrated terminal
is now completely plain ASCII without any ANSI colors.

Previously the same project and ESP-IDF setup showed colored output
(warnings in yellow, errors in red, colored section headers).

Additionally, the final memory usage table (ESP-IDF Size output) used to be displayed
with a fixed grid layout and colored text. Now it is shown as a completely plain
monochrome ASCII table without any coloring or enhanced formatting.

The build itself is successful and environment is correct.
Only the colorized output and enhanced formatting in the VS Code integrated terminal are missing.

Expected behaviour:
ESP-IDF build output should contain ANSI colors and enhanced formatting as in previous versions.

Debug Message

No runtime error. Only issue is missing ANSI colored output in VS Code integrated terminal.

Other Steps to Reproduce

After a clean Windows reinstall and fresh ESP-IDF 5.5.2 setup using the official
VS Code ESP-IDF extension, the build output in the VS Code integrated terminal
is now completely plain ASCII without any ANSI colors.

Previously the same project and ESP-IDF setup showed colored output
(warnings in yellow, errors in red, colored section headers).

Additionally, the final memory usage table (ESP-IDF Size output) used to be displayed
with a fixed grid layout and colored text. Now it is shown as a completely plain
monochrome ASCII table without any coloring or enhanced formatting.

The build itself is successful and environment is correct.
Only the colorized output and enhanced formatting in the VS Code integrated terminal are missing.

Expected behaviour:
ESP-IDF build output should contain ANSI colors and enhanced formatting as in previous versions.

                        Memory Type Usage Summary                             

+--------------------------------------------------------------------------------+
| Memory Type/Section | Used [bytes] | Used [%] | Remain [bytes] | Total [bytes] |
|---------------------+--------------+----------+----------------+---------------|
| Flash Code | 767594 | | | |
| .text | 767594 | | | |
| Flash Data | 206812 | | | |
| .rodata | 206556 | | | |
| .appdesc | 256 | | | |
| DIRAM | 145579 | 42.6 | 196181 | 341760 |
| .text | 101051 | 29.57 | | |
| .bss | 24144 | 7.06 | | |
| .data | 20384 | 5.96 | | |
| IRAM | 16384 | 100.0 | 0 | 16384 |
| .text | 15356 | 93.73 | | |
| .vectors | 1028 | 6.27 | | |
| RTC SLOW | 32 | 0.39 | 8160 | 8192 |
| .force_slow | 32 | 0.39 | | |
| RTC FAST | 24 | 0.29 | 8168 | 8192 |
| .rtc_reserved | 24 | 0.29 | | |
+--------------------------------------------------------------------------------+

I have checked existing issues, online documentation and the Troubleshooting Guide

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[Fabricio-ESP]

Hi @OK1TK , thanks for the report.
We will investigate how the latest changes affected the terminal on Windows machines, once we have a better understanding we will let you know.

[igittigitt]

I can add that the same problem exists, even without reinstalling everything and using ESP-IDF v5.5.1. If i open a "ESP-IDF Terminal" and use "idf.py build" it works with ANSI-colors, but not using the "wrench" icon. The latter one shows "Build successful" even if the output shows errors.

[OK1TK]

I can add that the same problem exists, even without reinstalling everything and using ESP-IDF v5.5.1. If i open a "ESP-IDF Terminal" and use "idf.py build" it works with ANSI-colors, but not using the "wrench" icon. The latter one shows "Build successful" even if the output shows errors.

I tried was not able to do it even with the terminal. The output looks the same if I use SHIFT+CTR+P -> ESP-IDF Terminal or the wrench icon. May be I am doing something wrong.

I can just confirm that the the commands itself are in different colors in the terminal window. E.g.: idf.py (yellow) build (standard white), idf.py (yellow) -v (grey) build (white). Everything elese running as putput is pure white text.

[bu-butterfly]

I was originally using an older version of VS Code (1.85.1), but because I wanted to use the CodeX plugin, I updated VS Code to version 1.107.1. Now, all the errors and warnings from espidf (5.5.1) are white.

[Smity]

I have two Win11 machines with the same problem. Doctor output added for good measure.

report.txt