[BUG] claude agents: cursor not visible in typing window on first session attach (Windows Terminal, Windows 11, 2.1.169)
Status Fixed / completed
Reported on v2.1.169
Maintainer reply None cached
Activity 10 comments · opened Jun 9, 2026 · closed Jun 15, 2026
Description
When attaching to any session via claude agents, the typing/input window renders with no visible cursor. Typing is fully functional — input is accepted and messages send normally — but the missing cursor makes editing difficult.
Steps to Reproduce
- Run
claude agents - Select any session and attach
- Observe typing window — no cursor visible
100% reproducible on first attach.
Expected Behavior
Cursor visible and positioned in the typing window input area.
Environment
- Claude Code: 2.1.169
- OS: Windows 11 Pro (build 26200)
- Terminal: Windows Terminal — reproducible under both Command Prompt and PowerShell profiles
Notes
Typing works — cursor is missing visually only.
Related: #66275 (same symptom, different trigger: post-subagent vs first attach), #65989 (2.1.163 cursor regression), #65558 (agents keyboard regression, separate).
10 Comments
Reproducing on 2.1.170, Windows 11 Pro 10.0.26200, Windows Terminal + PowerShell 7. Same symptom: the
claude agentslist view shows the cursor fine, but after attaching to a session the input window has no visible cursor (typing/sending still works). 100% repro on attach.@0x0A-H0XT0N meanwhile, if we use normally chat not "agents" mode, it's showing up the cursor (caret) on the terminal same condition with Windows Terminal + PowerShell 7.6.2
Still present on 2.1.172, same env (Windows 11 Pro 10.0.26200, Windows Terminal + PowerShell 7). Repros everywhere inside the agents view - attached session, bg session, and chat tab all render the input with no visible cursor. Still 100% on attach.
Confirming @devhardiyanto observation: a regular
claudesession in the same terminal shows the caret fine, so this is specific to the agents view input.Nothing in the 2.1.170-2.1.172 release notes appears related (closest are the /model dispatch-input fix and the Windows mouse-tracking change in 2.1.172 - neither touches this).
Yeah, checked the release notes too the cursor fix in 2.1.172 is about mouse tracking, not the caret issue. Still happening here on Windows Terminal + PowerShell 7.6.2. Doesn't look like it's been addressed yet.
Still present on 2.1.173, same env (Windows 11 Pro 10.0.26200, Windows Terminal + PowerShell 7). Same shape: the agents list view shows the cursor fine, attaching to a bg session renders the input with no caret, and a standalone
claudesession in the same terminal still shows it fine.Nothing in the 2.1.173 notes looks related (only the
[1m]model-ID normalization and a Windows sandbox startup-warning fix).is there any workaround for this at the moment? we basically enter "agents mode" as we start a new chat, so there is no way to actually stay in "chat mode"?
this appears to have been fixed for me in v2.1.177
Fixed in v2.1.177 for me too.
great, thank @jdu2600 @ajbisberg and you need to test on v2.1.177 as well bro @0x0A-H0XT0N
I'm still seeing this issue on MacOS (2.1.220 (Claude Code)) - its very annoying.