CLI startup: typed message disappears with no loading/working indicator for a long time

Problem

When starting a new Claude Code CLI session, there's often a long delay before anything happens — I type my message, hit enter, and it just vanishes from the input. There's no spinner, "thinking", "connecting", or any indicator that something is happening in the background. This can last a long time ("yonks") with zero visible feedback, making it look like the input was lost or the app is frozen.

This may be related to session/model cold-start cost (see #81657 — Fable-as-default causing ~5min startup), but happens broadly enough that it feels like a separate/general issue with the startup and input-submission UX.

Requested fix

Show a persistent loading/working indicator as soon as a message is submitted, so it's always clear the CLI is alive and working rather than looking like input was dropped — especially during whatever startup/connection work happens before the first response streams in.

Environment

• Claude Code CLI, Windows 11