[BUG] Claude CLI view in Eclipse plugin loses input focus after response; clicking inside view does not restore it

Environment

• Claude Code CLI: 2.1.114
• Claude Code for Eclipse IDE: 2.2.3 (com.anthropic.claudecode.eclipse.feature.feature.group, provider: eilonwy06)
• Eclipse IDE: for Java Developers (includes Incubating components), Version 2026-06 M1 (4.40.0 M1), Build 20260409-0738
• Java runtime: Eclipse Adoptium 21.0.5+11-LTS
• OS: Windows 11 Business, Build 26200 (x86_64/win32)

Description

After Claude finishes generating a response (or during a tool call), the Claude CLI view in Eclipse stops receiving keyboard input. The prompt appears frozen:

• Keystrokes are not registered in the input
• The cursor stops blinking in the prompt
• Clicking inside the Claude CLI view does NOT restore focus

The only workaround is to click on a sibling tab in the same view stack (e.g., History or Search) and then click back to Claude CLI. Focus is then restored and typing works again — until the next response completes, at which point the issue recurs.

Steps to reproduce

1. Open Eclipse 2026-06 M1 with Claude Code for Eclipse IDE 2.2.3 installed
2. Open the Claude CLI view (appears as a tab alongside History, Search, etc.)
3. Send any prompt (e.g., "hello")
4. Wait for Claude to finish responding
5. Try to type the next prompt → no input is accepted, cursor does not blink
6. Click the Claude CLI view → focus is still not restored
7. Click the History tab (or any sibling tab), then click back to Claude CLI → focus returns

Expected behavior

After a response completes, the prompt input should retain (or regain) keyboard focus so the next message can be typed without manual focus workarounds.

Actual behavior

Focus is lost after each response and cannot be reclaimed by clicking the Claude CLI view itself; only a detour through another tab restores it.

Additional notes

• Running on an Eclipse milestone build (2026-06 M1), which may be relevant to SWT focus handling.
• Possibly related to v2.1.113 change that switched to spawning native binaries instead of bundled JavaScript.
• Possibly related to terminal-state regression #50531 on Windows.