Repository navigation
Conversation
Keep legacy grants limited and preserve existing file and memory read restrictions. Disclose short-lived Git access and cover consent, reconnect, plugin dispatch and revocation. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Gil Birman <gil@squareup.com>
Distinguish built-in read restrictions from enabled plugins’ existing host permissions and cover plugin-owned file access through the external connection. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Gil Birman <gil@squareup.com>
Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Gil Birman <gil@squareup.com>
Preserve consent text and dispatch behavior while consolidating the full-access branch and shared cursor guard. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Gil Birman <gil@squareup.com>
Contributor
Author
|
🤖 @builderbot review |
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
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.
Superseded by #2707, which merged the Connect to Buzz authorization fix into
main. This duplicate PR is closed in favor of that implementation.Choosing Connect to Buzz in Nexus opens an authorization link requesting
agentaccess. Buzz only accepted the older limited scopes, so it rejected the link with “This link doesn’t work” before showing approval. Acceptagentas an exclusive scope in incoming links and saved approvals, then use Buzz’s existing tool dispatcher and enabled plugin tools after the owner approves.Existing limited grants keep their current access. Buzz’s built-in file and memory reads remain unavailable; enabled plugin tools retain their approved host permissions. Consent explains those permissions, channel checks, tool confirmations, and the short-lived Git credentials that repository tools can return. Regression coverage checks startup link handling, consent, exact saved scopes, plugin dispatch, and revocation. Native simulated deep-link ingress now opens consent; Deny returns a valid denial without a grant. Full pairing and tool discovery are blocked by the debug identity’s conflict with the existing Block account binding. Human acceptance remains pending. The PR remains a draft until the repository’s acceptance checklist is complete.