Skip to content

[Bug]: ANSI Code Broken Render in CLI #59397

Description

@CooperWang0912

Bug Description

When running hermes setup or similar commands such as hermes model, the interactive wizard fails to render terminal colors and box-drawing elements correctly. The ANSI escape sequences (like [35m and [0m) are being printed as literal text prefixed by an unparseable character string rather than being interpreted by the terminal. This happens in both CMD and Powershell.

Screenshots

Image Image

Steps to Reproduce

  1. Open Windows Terminal (PowerShell or CMD).
  2. Run hermes setup.
  3. Observe broken render for the CLI.

Expected Behavior

The terminal should interpret the escape codes to render colored text and borders cleanly without displaying raw [35m or [0m strings.

Actual Behavior

The CLI render is broken.

Affected Component

Setup / Installation

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

Report     https://paste.rs/ahl1H
agent.log  https://paste.rs/sduw

Operating System

Windows 10

Python Version

3.12.10

Hermes Version

0.18.0 (2026.7.1)

Root Cause Analysis

This is likely caused by incorrect ANSI setup in the installer script. I will look into it and see if I can locate the exact issue.

Proposed Fix

Replace faulty ANSI setup with the correct rendering code.

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium — degraded but workaround existsbugcomp/cliCLI entry point, hermes_cli/, setup wizardplatform/windowsNative Windows-specific behavior or breakagetype/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions