v0.2.45

v0.2.45 — Form inputs self-heal from dead page focus (Windows IME)

Release date: 2026-08-05
Previous version: v0.2.44

TL;DR

Fixes the Windows desktop app bug where, after interacting with a terminal, clicking into form inputs (e.g. the "New Terminal" form's title and prompt fields) did nothing — no caret, no typing, no matter how many times you clicked. Inputs now detect the dead-focus state and rebind keyboard focus on the spot.

Highlights

Clicking a form input now always activates it

On Windows, working inside an xterm terminal could leave Chromium's page focus dead while the OS kept routing clicks and keys to the window. In that state a click on a form input moved DOM focus but never activated the caret, and the existing recovery paths couldn't reach it: the app-level reset was a no-op on an already-focused window, the New Terminal form only ran its focus handoff once on open, and the terminal's self-heal only covered the terminal itself.

The app-level focus bridge now detects input arriving while page focus is dead (on click, key press, or focus change) and runs the proven forced rebind sequence — blur → forced IME reset → refocus the clicked target. This applies to every form input in the app (New Terminal form, Planner, settings, etc.), not just the reported one. The forced reset only fires in the dead-focus state, so healthy Korean IME composition is untouched.

Install / Update

npm i -g clitrigger@0.2.45

Desktop app — pick the right asset:

• Windows (recommended): CLITrigger-Setup-0.2.45.exe — installer with Start Menu shortcut, uninstaller, and auto-update.
• Windows (portable): CLITrigger-0.2.45.exe — run directly, no install; no shortcuts and no auto-update (grab new versions manually).
• macOS: .dmg / Linux: .AppImage

Full commit list

• 9298cb7 fix(ime): 폼 인풋 클릭이 죽은 페이지 포커스를 자가 복구 — 새 터미널 폼 입력 불가 해소

Related docs

• Detailed changelog — per-date technical decision records

Full Changelog: v0.2.44...v0.2.45