Diagnose an AWF (Agentic Workflow Firewall) failure from an error, workflow run URL, or symptom. Covers auth (api-proxy, enterprise/BYOK Copilot, OIDC, mcpg), ARC/DinD and self-hosted runners, alternative runtimes (gVisor/Kata/chroot), Squid/DNS/egress denials, CI and gh-aw safe-output failures, and suspected security regressions. Routes to the canonical diagnosis registry in docs/diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Single entry point for diagnosing AWF failures. The canonical knowledge lives in the diagnosis registry — this skill only routes and reports.
Read the index — docs/diagnostics/README.md
for boundary routing and specialist references, and
docs/diagnostics/agent-playbook.md
for the report shape and safety rules.
Fingerprint the run: AWF version, runner type (GitHub-hosted /
self-hosted / ARC+DinD / GHES / GHEC), DOCKER_HOST, GITHUB_SERVER_URL,
container runtime, provider, auth mode. Use unknown where unverified.
Classify the failing boundary: runner, runtime, network, auth,
ci, security.
Load only matching records:
npx tsx scripts/diagnostics/cli.ts search "<redacted error string>" --boundary <boundary>
Without a clone, use the portable artifact
.github/agents/diagnose-awf.md (prefer a tag matching your AWF version).
Probe with the matched finding's read-only probe when the match is ambiguous — one probe at a time.
Report: observed symptom, matched finding ID and evidence, affected version/topology, safe next probe, fix/workaround, citations.
AUTH-001, AUTH-002AUTH-001, docs/auth-matrix.mdAUTH-003Check configuration presence/shape, route and health status, and redacted error classes only.
Authorization headers, environment
dumps, inference probes, or token exchanges.--env-all, disabling isolation, or broadening the domain
allowlist by default.SEC-001 and
the repository security review process..github/workflows/shared/self-hosted-failure-modes.md — full runner catalog.github/skills/debug-firewall/SKILL.md — Squid, iptables, container state.github/skills/awf-debug-tools/SKILL.md — log parsing helpers.github/skills/debugging-workflows/SKILL.md — GitHub Actions log retrievaldocs/auth-matrix.md, docs/compatibility.md, docs/troubleshooting.mdFollow docs/diagnostics/patterns.md.
Edit the canonical record, run npm run diagnostics:render, and open a reviewed
PR. Never edit generated artifacts or .lock.yml files by hand.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Decide and implement how to support a new LLM provider or agent engine in AWF - either as a proxied provider (api-proxy adapter) or a direct-API engine (domain allowlist only), e.g. Cursor, Aider, or any tool that calls its own endpoint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Practical Python scripts for debugging awf - parse logs, diagnose issues, inspect containers, test domains
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the AWF (Agentic Workflow Firewall) to run commands with network isolation and domain whitelisting. Provides L7 HTTP/HTTPS egress control for AI agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug the AWF firewall by inspecting Docker containers (awf-squid, awf-agent), analyzing Squid access logs, checking iptables rules, and troubleshooting blocked domains or network issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug GitHub Actions workflows by downloading logs, analyzing summaries, and understanding how agentic workflows and the AWF firewall work together.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.