What GitHub changed on September 9
GitHub's September 9, 2026 announcement introduced central controls that let Copilot Business and Enterprise administrators classify agent operations as blocked, approval-required, or allowed without prompting. The managed rules cover shell commands, file reads and edits, and network domains. A managed restriction cannot be weakened by a user or workspace setting, auto-approval, bypass mode, or a saved approval.
The controls are generally available in the GitHub Copilot app, GitHub Copilot CLI, and Visual Studio Code sessions using Agent Host. They do not automatically apply to every IDE or Copilot host. JetBrains has separate enterprise sandbox functionality.
Why deterministic validation belongs on the allowlist
An agent can produce syntactically plausible JSON or XML that still violates a schema, uses the wrong type, omits a required property, or breaks a reference-dependent constraint. A deterministic validator gives the workflow a repeatable pass/fail result and focused diagnostics. The agent can correct the specific problem and rerun the same check instead of treating generated text as proof of validity.
This is a good fit for narrow permissions: local validation needs a known executable, a reviewed command shape, and read access to the selected inputs and schema graph. It does not need general shell authority, a writable workspace, or unrestricted internet access.
The valbuddy-cli security model
- The Agent Plugin contains an MIT-licensed skill and PowerShell wrappers, but no executable, MCP server, hook, background service, downloader, or credential store.
- The separately installed proprietary
valbuddy.exeperforms JSON, JSON Schema, and XML validation locally on Windows. - Ordinary validation reads selected inputs and schemas and writes no output file.
- Customer documents are not uploaded to JSONBuddy for ordinary local validation.
- Remote
$ref, schema, DTD, import, or include resolution can require access to document-selected domains. - Installation and updates use GitHub; downloading the executable and checksum uses
www.json-buddy.com. The JSONBuddy Web API is not used for local validation. - Core validation is permanently free for commercial and personal use; specifically listed advanced and large-data operations have separate license requirements.
Start with a read-only validation policy
- Deploy an approved JSONBuddy portable package and record its SHA-256.
- Install
valbuddy-cli@jsonbuddyfrom the JSONBuddy-owned marketplace and pin its source to a reviewed full commit SHA when change control requires it. - Allow only the actual PowerShell wrapper or
valbuddy.exe -v/-wfcommand prefixes observed in your client. - Grant reads only to the project inputs, schemas, and local reference roots required by the workflow.
- Leave edits and network domains approval-gated. Add a write root only for a reviewed generation task, and add remote domains only when the schema graph needs them.
GitHub documents the policy selectors and precedence, but command strings and paths remain deployment-specific. The canonical deployment guide provides the verified permission matrix and a placeholder-based managed-settings example without pretending one policy file fits every host.
Install and validate in about 30 seconds
copilot plugin marketplace add Clemens-U/jsonbuddy
copilot plugin marketplace browse jsonbuddy
copilot plugin install valbuddy-cli@jsonbuddy
copilot plugin list
Then replace the paths in this prompt: Use valbuddy-cli to validate C:\path\data.json against C:\path\schema.json.
For Visual Studio Code and the GitHub Copilot app, use the JSONBuddy marketplace installation instructions. The plugin is maintained by JSONBuddy; its availability through Copilot does not mean GitHub reviewed, approved, certified, or endorsed it.
Put a narrow local check between generation and delivery
Install valbuddy-cli, approve the exact validation command and project read roots, and require a successful local check before an agent finishes work on generated JSON, JSON Schema, or XML.