[writingdeveloper]

What

• Claude Code's own status (OSC 7501). Claude Code 2.1.295+ reports idle/working/blocked(permission|question|auth)/done/error, but only to a terminal that answers its OSC 7501;? probe.
  • The host answers the probe once, before any viewer sees the output.
  • The renderer parses the reports with an xterm OSC handler. The header shows a status pill, the sidebar activity follows the report, and attention notifications say why.
  • Windows: Windows' ConPTY answers the DA1 that follows the probe and drops OSC input, so the probe is never answered. Sessions therefore run on node-pty's bundled conpty.dll (OpenConsole 1.22), but only when Settings → Claude status signal (experimental) is on. If the dll is missing, sessions fall back to Windows' ConPTY.
  • macOS/Linux: always on.
• What's new. A dialog appears once after an upgrade and lists features newer than the last version seen. Show me navigates there and rings the target. It is not shown on a first run (no saved window bounds). It is reachable from Settings → About.
• NEW dots. New buttons carry a dot until first used.
• Fix: withTreeKill dropped the bundledConpty flag.

Verified

• Real Claude Code 2.1.306 in a temp folder:
  • With the bundled ConPTY, the probe was answered and the reports arrived: idle → working → done (msg).
  • With Windows' ConPTY, the reply never reaches the child. This was reproduced with a minimal echo child.
• Packaged win-unpacked: the dll is found through the app.asar path, and the probe reply reaches the child.
• Tests: tsc; vitest 1490 passed.
• Screen tests:
  • qa:cockpit-tools 9/9 in dev and 9/9 against the packaged exe, with every check running on the bundled ConPTY.
  • qa:image-rows, qa:images, qa:images-remote, qa:perf-gate, qa:audit (0 a11y violations) and qa all pass.
• Release workflow: now runs qa:cockpit-tools against the packaged Windows app.

🤖 Generated with Claude Code

https://claude.ai/code/session_016NLGwiBY5uEivJqERQzcoY