Respect terminal cursor settings (shape, color)

[desaflow]

Problem

Claude Code uses Ink's fake cursor rendering which completely overrides the terminal's cursor settings. The real terminal cursor is hidden via \x1b[?25l and replaced with a chalk.inverse space character — always a white block, regardless of what the user has configured in their terminal.

This means:

• cursorShape: "bar" in Windows Terminal settings → ignored
• cursorColor: "#CC0000" → ignored
• Any cursor customization in any terminal emulator → ignored

Expected behavior

Claude Code should respect the terminal's native cursor settings (shape, color, blink) the same way every other CLI tool does.

Current workaround

Patching cli.js directly to change H1.inverse to H1.bgRgb(r,g,b) — works but gets overwritten on every update.

Suggested fix

Either:

1. Add a config option (cursorStyle: "native") that disables the fake cursor and uses the real terminal cursor positioned at the input caret
2. Add cursor color/shape settings to Claude Code's config (~/.claude/settings.json)
3. At minimum, read the terminal's cursor color from the color scheme rather than hardcoding inverse (white)

Environment

• Claude Code v2.1.63
• Windows Terminal on Windows 11
• Also affects any terminal emulator with custom cursor settings

[github-actions]

Found 3 possible duplicate issues:

1. Allow configuring terminal cursor style (block/bar/underline) #29133
2. Add cursor style configuration for input field #16086
3. Feature Request: Add environment variable to disable cursor shape changes #10534

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #29133.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.