Remove bounded-queries from instruction files - #51339
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
PR Triage
Removes stale
|
There was a problem hiding this comment.
Pull request overview
Note
Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.
Removes documentation and guidance for tools.github.bounded-queries (bounded private cross-repo Q&A) from the Agentic Workflow docs.
Changes:
- Deleted the
tools.github.bounded-queriesschema/docs section from the syntax reference. - Removed bounded-queries entries from the “designer mappings” and workflow creation guidance.
- Simplified cross-repository workflow instructions to only describe the unbounded/cross-repo-auth path.
Show a summary per file
| File | Description |
|---|---|
| .github/aw/syntax-agentic.md | Removes the bounded-queries configuration documentation from the main syntax reference. |
| .github/aw/designer-mappings.md | Removes bounded-queries recommendations from tool/pattern mapping tables. |
| .github/aw/create-agentic-workflow.md | Removes finite/bounded cross-repo guidance and leaves only unbounded access instructions. |
Review details
Tip
Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
| For cross-repository workflows, first determine whether the question is **finite and bounded**: | ||
|
|
||
| - If the agent needs to answer a finite, pre-approved question about a private repository (e.g. "does this repo have open critical issues?", "what is the latest release version?"): | ||
| - Use `tools.github.bounded-queries` with `private-repos` and `sandbox.agent.id: awf` (AWF v0.27.44+) | ||
| - This is the preferred approach — no raw source code is exposed and no cross-repo token is needed | ||
| - Select `runtime: sbx` only when experimental, capability-gated execution is intended. Each query gets a separate sbx VM; AWF fails closed during host preflight and never falls back to Docker or gVisor. | ||
| - If the answer is unbounded (e.g. arbitrary source-code extraction, full file contents), or if bounded queries are not appropriate: | ||
| - If the answer requires arbitrary source-code extraction, full file contents, or other unbounded access: | ||
| - enable the GitHub toolsets needed to read external repositories | ||
| - configure cross-repo authentication in `safe-outputs:` | ||
| - tell the agent to set `target-repo` |
|
🎉 This pull request is included in a new release. Release: |
Purges all references to
tools.github.bounded-queriesfrom the.github/aw/instruction files, which were describing a feature that no longer exists or should no longer be surfaced to authors.Changes
syntax-agentic.md: removed the fulltools.github.bounded-queriessubsection — schema, sensitivity levels (public/internal/confidential/sealed), andsbxruntime notescreate-agentic-workflow.md: removed the bullet recommendingbounded-queriesfor finite cross-repo questions; simplified the multi-repo guidance to a single path (grant toolsets + cross-repo auth)designer-mappings.md: removed both intent→pattern mapping rows that pointed tobounded-queries