fix: Remove bold styling from prompt on Windows to prevent cursor shift

[ConstantTime]

Summary

• Fixes Cursor shifted to the right using native windows CLI #3364 - Cursor shifted to the right using native Windows CLI
• Removes bold ANSI escape code from the prompt specifically on Windows terminals
• Maintains existing styling on other platforms (macOS, Linux)

Problem

When running Goose CLI on Windows 11, the cursor was shifted to the right in the terminal due to the bold ANSI escape code not being handled correctly by Windows terminals.

Solution

Added a platform-specific check using cfg\!(target_os = "windows") to conditionally apply styling:

• Windows: console::style("( O)>").cyan() (no bold)
• Other platforms: console::style("( O)>").cyan().bold() (with bold)

Test Plan

• Code compiles successfully (cargo check -p goose-cli)
• Tested on macOS - original behavior preserved
• Needs testing on Windows to confirm cursor position is fixed

Note

This is a draft PR as I don't have access to a Windows machine to test the fix. Would appreciate if someone with Windows could verify the cursor position is now correct.

[thebristolsound]

I was just in the process of debugging this issue myself and came across this PR. This bug renders the CLI unusable for me (no pun intended).

Wondering if this is something that can be enabled / disabled, like have an option to disable prompt styling if it's causing rendering issues. I'd rather have it fall back to safe defaults.

I'm honestly surprised more people haven't reported it.

[ConstantTime]

I was just in the process of debugging this issue myself and came across this PR. This bug renders the CLI unusable for me (no pun intended).

Wondering if this is something that can be enabled / disabled, like have an option to disable prompt styling if it's causing rendering issues. I'd rather have it fall back to safe defaults.

I'm honestly surprised more people haven't reported it.

Hey @thebristolsound
Thanks for the insight and sorry for late reply. Were you able to test the build out of this PR on your windows machine? We can get this fix in if we have a working proof for this.

[thebristolsound]

I'll get local dev setup and test it out, will let you know

[ConstantTime]

I'll get local dev setup and test it out, will let you know

Thanks!

[thebristolsound]

Just a heads up, I went ahead and created a pull request addressing this issue and added some test coverage onto it. Got two approvals and just waiting for next steps:

#4464

[ConstantTime]

Just a heads up, I went ahead and created a pull request addressing this issue and added some test coverage onto it. Got two approvals and just waiting for next steps:

#4464

Cool. Closing my PR then.