Repository navigation
Default read-only agent workflows to no network access - #68047
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Explore agent personas for custom workflows
Default read-only agent workflows to no network access
Oct 12, 2026
pelikhan
marked this pull request as ready for review
October 12, 2026 19:26
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
A final single-persona run generates only two scenarios but still requires at least three.
1 open finding
What changed in this PR
Adds no-network guidance for read-only workflows and improves persona rotation.
Changes:
- Recommends
network.allowed: []for repository-only inspection. - Preserves final unexplored personas before rotation reset.
- Adds documentation contract tests.
Security review found no weakened protections; scanner execution was unavailable.
| File | Description |
|---|---|
.github/workflows/smoke-claude-routed.lock.yml |
Refreshes generated runtime dependencies. |
.github/workflows/agent-persona-explorer.md |
Updates persona rotation and scenario guidance. |
.github/workflows/agent-persona-explorer.lock.yml |
Refreshes generated workflow metadata. |
.github/skills/agentic-workflows/tests/test_guidance.py |
Tests network and rotation guidance. |
.github/aw/workflow-constraints.md |
Establishes the read-only no-network default. |
.github/aw/create-agentic-workflow.md |
Adds structural network-denial guidance. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
| ## Phase 3: Test Agent Responses (15 minutes) | ||
|
|
||
| **Token Budget Optimization**: Test all 4 scenarios in the initial baseline. On later runs, test a **representative subset of 3-4 scenarios** from the 6 generated (not all) to reduce token consumption and ensure budget remains for Phase 5 publishing. | ||
| **Token Budget Optimization**: Test all 4 scenarios in the initial baseline. On later runs, test a **representative subset of 3-4 scenarios** from those generated (not all) to reduce token consumption and ensure budget remains for Phase 5 publishing. |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.

Persona exploration found inconsistent network recommendations for read-only workflows: one compliance check allowed default egress despite needing none. It also identified two personas that the explorer’s rotation would skip before resetting.
Network guidance
network.allowed: []for in-repo inspection and GitHub reads throughgh-proxy.Persona rotation