The GitHub Actions job "prek" on airflow-steward.git/claude-term-bg-helper has 
succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
79abe62956a53b330cbf8bd2dae38eb7bebd2018 / Jarek Potiuk <[email protected]>
feat(agent-isolation): add opt-in terminal-tint helper for waiting state

Ship claude-term-bg.sh, an optional quality-of-life helper (not a
security control) that keeps a calm baseline terminal background and
tints it only when Claude Code genuinely wants the operator to act —
never while it is working.

Two states across five user-scope hooks: Stop -> wait (turn finished,
tint); Notification -> notify (tint only for permission prompts, calm
for the plain idle ping); and PreToolUse + UserPromptSubmit +
SessionStart -> reset (calm while working, after a reply, and on a
fresh session — SessionStart also clears a stale tint a prior session
left in the terminal).

Two mechanics the helper gets right and the doc explains:

- Hooks run with no controlling terminal, so /dev/tty is useless;
  find_tty_dev() walks the process tree to the Claude pty and writes
  the OSC escape there.
- iTerm2 honours OSC 11 (set) but not OSC 111 (reset), so the only
  deterministic reset is an explicit colour via CLAUDE_RESET_BG; the
  fallback emits OSC 111 plus iTerm2's SetColors=bg=default.

Wires into the secure-agent-setup doc as an explicitly-optional,
default-off install step (asked during setup, mirroring the status
line), with the helper added to the agent-isolation README and a new
"Waiting-for-input terminal tint" section (Install / Verify /
Trade-offs). Framed throughout as a UX convenience, not a security
mechanism.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

Report URL: https://github.com/apache/airflow-steward/actions/runs/27023403070

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to