You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jobs@airflow.apache.org by GitBox <gi...@apache.org> on 2026/04/30 09:57:11 UTC

[GH] (airflow-steward/docs-secure-setup-bypass-hook): Workflow run "prek" is working again!

The GitHub Actions job "prek" on airflow-steward.git/docs-secure-setup-bypass-hook has succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
795f69ab814e1b9442a9b5877c62047158e06c68 / Jarek Potiuk <ja...@potiuk.com>
docs(secure-agent-setup): sandbox-state status line for the terminal footer

Adds a `statusLine` helper that makes the active sandbox state of
the current Claude Code session visible at all times — green
`[sandbox]` when `sandbox.enabled: true` is set in the resolved
`settings.json`, bold-red `[NO SANDBOX]` otherwise. The indicator
sits in the terminal footer that Claude Code already renders, so
no extra UI surface is added; it just makes the existing footer
informative about the *one* configuration property the rest of
this document is about.

Why it is needed even with the existing sandbox-bypass-warn hook:
the `PreToolUse` hook fires per-call when the model requests a
bypass, but a session whose `sandbox.enabled` was simply never set
(e.g. an unrelated project's `.claude/settings.json` is missing,
the user is in `~`, settings drift after a Claude Code upgrade)
emits no signal until something goes wrong. The status line covers
that gap by surfacing settings-level state continuously.

Three changes:

- `tools/agent-isolation/sandbox-status-line.sh` — the helper.
  Reads the statusLine JSON on stdin, resolves
  `.sandbox.enabled` from project- then user-scope `settings.json`
  via `jq`, prints `<model> [sandbox]` (green) or
  `<model> [NO SANDBOX]` (bold red). ASF license header matching
  the sibling scripts; executable bit set.
- `secure-agent-setup.md` — new H2 "Sandbox-state status line"
  between the bypass-warn hook section and the sync-config section
  (sibling user-scope observability features). Adopter step 5 now
  recommends both, the sync-config layout, "what to track" table
  and fresh-host setup snippet pick up the new script. TOC entry
  added by hand following the same encoding rule as the previous
  TOC regen — anchor `#sandbox-state-status-line`.
- `tools/agent-isolation/README.md` — Files table picks up the
  new script.

Trade-offs are documented in-line: the indicator is settings-level
truth, not session-level truth (CLI flags like
`--bypass-permissions` and runtime mode changes that override the
file are not visible), and pairing with the per-call bypass-warn
hook is the recommended belt-and-braces posture. A future Claude
Code statusLine schema that exposes sandbox state directly would
let the helper drop the file-read.

Generated-by: Claude Code (Claude Opus 4.7)

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

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: jobs-unsubscribe@airflow.apache.org
For additional commands, e-mail: jobs-help@airflow.apache.org