Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[aw] Smoke Copilot Network Isolation is missing required tool

Closed
  • Is something wrong?
#9,086 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash, github-actions
Domain
ci-cd, security

Research direction

Start with .github/workflows/smoke-copilot-network-isolation.md and the failed run 36337338142, then read debug.md and the agentic-workflows skill referenced in the issue. Reproduce the two curl checks in the sandbox and determine why bash permissions are denied; done means the workflow can obtain valid egress results without the engine terminating unexpectedly.

Written by the indexing model from the issue text.

Description

agentic-workflows
Workflow Failure

Workflow: Smoke Copilot Network Isolation
Branch: copilot/refactor-sbx-manager-tests
Run: https://github.com/github/gh-aw-firewall/actions/runs/36337338142
Pull Request: #9078

[!WARNING]
Missing Tools Reported: The agent reported missing tools during execution.

Missing Tools:

  • bash/curl execution: bash tool denied executing curl commands ("Permission denied and could not request permission from user") for both egress checks, preventing verification of allow/deny network isolation behavior.

Alternatives:

Tool Alternative
bash/curl execution Re-run workflow with bash tool permissions enabled, or manually run the two curl commands inside the sandbox and report results.

[!WARNING]
Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

● add_comment (MCP: safeoutputs) · body: "@lpcox Unable to complete smoke test — the bash tool deni…
  └ {"result":"success","temporary_id":"aw_rdA0EAKV","comment":"#aw_rdA0EAKV...
[safeoutputs-cli] hasTerminalSafeOutput: terminal entry found in /home/runner/work/_temp/gh-aw/safeoutputs/outputs.jsonl: type=add_comment
Both required curl checks were blocked by the sandbox before any network activity occurred ("Permission denied and could not request permission from user"), so no genuine egress verdict could be obtained. I reported this via `missing_tool` and posted a comment noting the inconclusive FAIL result with the required `EGRESS_RESULT` line.
Changes   +0 -0
Duration  16s
Tokens    ↑ 203.9k • ↓ 908 • 162.6k (cached)
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw-firewall/actions/runs/36337338142
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

[!TIP]

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Smoke Copilot Network Isolation · copilot · 14.5 AIC · ◷

  • expires on Oct 4, 2026, 5:36 PM UTC
Dominant language
TypeScript
Stars
149
Forks
77
Avg merge
4h 34m
Merged PRs (30d)
418

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw-firewall

All issues in github/gh-aw-firewall

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.