Feature request: blinking cursor option in CLI input box

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The input cursor in the Claude Code CLI is a steady block. Functionally fine — but for those of us who came up on blinking cursors, the blink isn't just aesthetic. It's tactile. The terminal is a liminal space, and the cursor blink is part of what makes it feel alive and ready.

The Windows accessibility cursor blink rate setting doesn't reach the Claude Code CLI input box — it's app-rendered, so this would need to be handled on your side.

A simple option would be enough: blink on/off, maybe blink rate. Nothing elaborate. Just give the old-school coders their campfire back. Liminial and Nostalgic like it was meant to be, or at least how it was in the days of Uncs and Olds.

Proposed Solution

A simple option would be enough: blink on/off, maybe blink rate. Nothing elaborate. Just give the old-school coders their campfire back. Liminial and Nostalgic like it was meant to be, or at least how it was in the days of Uncs and Olds.

Alternative Solutions

Have it default to the windows terminal settings.

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

The steady block cursor works but the blink would make the input line feel less dead between responses. Small thing, high comfort value for terminal-native users.

Additional Context

It reminds me of my younger days coding in terminal. Bringing this back is nice. I won't say it hurts my productivity, in fact, I think it helps it. It's pure, no distractions.
Liminal and Nostalgic and Clean.
I miss my blinky cursor. It's not a big thing, but sometimes, the small things unconsciously noticed are what give that extra nudge to get someone to use your product over someone else's. Though I think the incredible lead Claude Code has on other LLM's in coding might be deciding that first. Still, doesn't hurt! Thank you for your time and consideration, regardless of whether it is feature that ends up landing.