Terminal output garbled/mojibake on Windows (PowerShell) during codegraph index

[starkleek]

Environment

• OS: Windows 11
• Node: v20.19.5
• codegraph: 0.7.9
• Terminal: ( Cursor integrated terminal / Windows Terminal / cmd)

Steps to Reproduce

1. codegraph init -i
2. codegraph index

Expected Behavior

Terminal output shows clean progress with colored text.

Actual Behavior

Output contains garbled characters (mojibake), for example:

[zhaorx]

me too

[colbymchenry]

Fixed in #178, will ship in 0.7.10.

Root cause: the shimmer progress renderer runs in a worker thread and writes to stdout via fs.writeSync(1, …) to keep the animation smooth while the main thread is blocked in SQLite. That path bypasses Node's TTY-aware UTF-8→codepage conversion on Windows, so glyphs like │ ◆ — hit your console as raw UTF-8 bytes and got reinterpreted by the active OEM codepage (CP437 / CP936 / …) — producing 鋍?[0m 鉒?[0m Scanning files 鈥?N found. Clack's output in the same screenshot rendered fine because clack writes through the main thread's TTY-aware path.

Fix: CodeGraph now picks an ASCII glyph set on Windows by default (| * - instead of │ ◆ —). The shimmer animation, status icons, and tree drawing all participate.

Escape hatches:

• CODEGRAPH_UNICODE=1 to opt back into Unicode (e.g. pwsh 7 where you've set [Console]::OutputEncoding to UTF-8)
• CODEGRAPH_ASCII=1 on any platform to force ASCII (useful for log collectors and non-TTY pipelines)

Workaround until 0.7.10 ships — for current versions on Windows PowerShell, set [Console]::OutputEncoding = [System.Text.Encoding]::UTF8 and chcp 65001 before running codegraph index. That fixes the console codepage so UTF-8 bytes render correctly.

Thanks for the report, and thanks to @Bortlesboat for the initial PR (#174).