Skip to content

Preflight required tools before agent execution - #76183

Draft
gh-aw-bot with Copilot wants to merge 3 commits into
mainfrom
copilot/add-preflight-required-tools-check
Draft

gh-aw-bot with Copilot wants to merge 3 commits into
mainfrom
copilot/add-preflight-required-tools-check

Conversation

Copilot AI commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Workflows can explicitly require tools their configuration does not expose, wasting an agent run before the mismatch surfaces. This adds compile-time validation and runtime preflight with actionable configuration errors.

  • Compiler: Validate explicit MCP tool instructions against effective servers, toolsets, allowlists, and transports. Keep alternatives, examples, and shell instructions advisory; never expand permissions automatically.
  • Runtime: Check recorded requirements against live, paginated tools/list responses before agent startup.
  • Workflow corrections: Align verified tool and transport mismatches, enable discussion comments and issue-field discovery where required, and make steering instructions transport-aware.
  • Documentation: Describe preflight behavior and inference limits; regenerate affected workflow locks.

For example, Call github(issue_read). fails compilation when issue_read is excluded. If configuration permits it but the live server omits it, runtime preflight stops execution before the agent starts.

Copilot AI and others added 2 commits November 9, 2026 08:05
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot AI changed the title [WIP] Add preflight check for required tools before agent execution Preflight required tools before agent execution Nov 9, 2026
Copilot AI requested a review from gh-aw-bot November 9, 2026 08:18
@@ -1,4 +1,4 @@
Before finalizing your work, use the GitHub MCP `issue_read` tool to read comments on the steering issue. Treat relevant user-authored comments containing the keyword `steer` as feedback for this run, and follow any protocol the user specifies in those comments when incorporating feedback into your implementation or final pull request body.
Before finalizing your work, read comments on the steering issue using the configured GitHub read interface: with `gh-proxy`, use `gh issue view <number> --comments --repo <owner>/<repo>`; otherwise use `issue_read` through MCP or its configured CLI wrapper. Treat relevant user-authored comments containing the keyword `steer` as feedback for this run, and follow any protocol the user specifies in those comments when incorporating feedback into your implementation or final pull request body.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[AW Top 10] 07 Preflight required tools before agent execution

3 participants