[Docs] Warn agents not to leak sensitive context on public GitHub surfaces#300
Merged
mrubens merged 1 commit intoJul 13, 2026
Merged
Conversation
Contributor
Author
mrubens
marked this pull request as ready for review
July 13, 2026 22:27
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 13, 2026 22:27
mrubens
deleted the
docs/open-source-public-surface-caution-1vw2eibhjdwy9
branch
July 13, 2026 22:27
brunobergher
pushed a commit
that referenced
this pull request
Jul 14, 2026
…faces (#300) Co-authored-by: Matt Rubens <2600+mrubens@users.noreply.github.com>
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.
What changed
Added an Open source and public surfaces section to the root
AGENTS.mdso agents treat GitHub and other public surfaces as fully public and avoid leaking customer names, private details, secrets, or internal maintainer discussion into commits, PRs, comments, or related public artifacts.Why this change was made
This repo is open source, so agent guidance needs an explicit guardrail: private task context must not spill onto public GitHub surfaces.
Impact
No product behavior change. Future agent work should keep customer-specific and internal discussion off public artifacts and prefer private channels for sensitive context.