Repository navigation
Automatically authorize new generated component builds and installations in ACP - #863
Open
Yosh (yoshuawuyts) wants to merge 1 commit into
Conversation
…ons in ACP Authorize new lineages at the shared ACP host boundary without editor prompts or provider-specific settings. Preserve explicitly enabled rebuild approvals, exact-revision tool execution authorization, and existing sandbox and transactional guarantees. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Yosh <github@yosh.is>
Yosh (yoshuawuyts)
added this pull request to stack #834
October 2, 2026 21:50
This branch has not been deployed
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.
ACP now builds and installs new generated tools and layers without host editor prompts, independently of the provider and without an opt-out. Sandbox isolation, validation and separate revision-bound tool execution approvals remain unchanged; explicitly enabled rebuilds still require both approvals. This intentionally removes per-operation confirmation for new generated components; no configuration migration is required.