Auto-allow breeze in the Claude Code isolated agent setup#69094
Open
potiuk wants to merge 1 commit into
Open
Conversation
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
breeze is the mandated entrypoint for all local development in this repo (the contributor instructions forbid running pytest/python/airflow directly on the host), so contributors using Claude Code's isolated/secure agent setup get a permission prompt on every breeze invocation. This adds a Magpie adopter override so the setup-isolated-setup-install skill seeds a per-machine breeze allow baseline (including the uvx/uv-run dev/breeze shim forms and read-only docker ps/info) into .claude/settings.local.json at install time — no shared committed settings file to maintain, and only non-destructive commands.
potiuk
changed the title
potiuk
force-pushed
the
add-claude-code-breeze-permissions
branch
from
158af78 to
ca39a8a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reworks this PR to use a Magpie adopter override instead of a committed
.claude/settings.json.Adds
.apache-magpie-overrides/setup-isolated-setup-install.mdso thesetup-isolated-setup-installskill (the Claude Code isolated/secure agent setup) seeds a per-machine breeze permission baseline into the gitignored.claude/settings.local.jsonat install time. breeze is the sanctioned way to run all local dev/test commands here (the contributor instructions forbid running pytest/python/airflow directly on the host), so without these allows every breeze invocation prompts for Bash permission.Covered:
breeze *, theuvx/uv run *dev/breeze*shim forms, the commonANSWER=yes/SKIP_BREEZE_SELF_UPGRADE_CHECKenv-prefixed wrappers, and read-onlydocker ps/docker info. Only non-destructive commands — nodocker rm, nonetwork prune.Why an override rather than a committed settings file:
.claude/settings.jsonto review/maintain (that path stays gitignored in this repo).Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines