Enterprise Configuration | GitHub Agentic Workflows
Skip to main content Enterprise Configuration Use this page to assess deployment and runner applicability, and to configure GitHub Enterprise Server (GHES) and GitHub Enterprise Cloud (GHEC) compatibility options. Deployment and runner applicability Section titled “Deployment and runner applicability” Choose the GitHub deployment and runner topology independently. GHEC organizations on github.com are not the same deployment as GHEC with data residency on *.ghe.com ; neither is GHES.
ARC describes runner infrastructure, not a GitHub deployment or an AI engine. GitHub deployment Implemented compatibility Evidence and product boundary github.com , including GHEC organizations Default GitHub and Copilot endpoint configuration Published product requirements , quickstart, and hosted Linux CI environment. This does not promise every engine, feature, or runner combination. GHEC with data residency ( *.ghe.com ) Tenant-specific endpoint routing and host/domain configuration Endpoint/configuration tests and tenant troubleshooting , not a live tenant validation matrix.
End-to-end availability for the selected engine and services is unconfirmed here. GHES (custom hostname) CLI host configuration, artifact/cache compatibility mode, and enterprise endpoint routing Compiler and endpoint tests, not a live GHES release matrix. End-to-end availability and a minimum GHES release are unconfirmed . Runner topology Component prerequisites Evidence and limitations GitHub-hosted Linux Docker/Compose and compatible Linux tooling gh-aw and AWF hosted CI; this is not enterprise-tenant or GHES validation.
GitHub-hosted runners are not available for GHES. Self-hosted Linux, shared runner/daemon filesystem Docker access; daemon-visible workspace, tool, and output paths Configuration path exists; hosted CI does not certify custom images, persistent state, or security policies. Validate the actual runner and selected engine. Self-hosted ARC/DinD, split runner/daemon filesystems Privileged DinD sidecar, shared work volume, accessible Docker socket, DOCKER_HOST , and sysroot staging Implemented split-filesystem path.
AWF live split-DinD checks are not Kubernetes ARC validation. End-to-end ARC deployment/chart combinations remain unconfirmed ; no minimum chart version is established here. For official runner availability, see GitHub-hosted runners . For firewall-specific applicability, see AWF environment and runner applicability , enterprise routing , and ARC/DinD configuration . AWF links back to this reference for stack-level applicability.
End-to-end availability and owner confirmation Section titled “End-to-end availability and owner confirmation” An end-to-end statement must cover the gh-aw compiler, selected engine and inference provider, MCP gateway and configured MCP servers, AWF, Actions runner, and dependent GitHub services : Actions workflow syntax, tokens/permissions, artifacts, caches, APIs, and any enabled Copilot services. A passing compiler test or accepted AWF schema establishes none of the other components’ availability.
GitHub’s published GHEC product requirements require Actions, an AI-engine account, and an authenticated CLI; they do not provide a GHES/ARC component-version certification. No owner-confirmed release-by-release support commitment is documented for GHES, data-residency tenants, or Kubernetes ARC. Those combinations remain unconfirmed; configuration examples alone do not establish support. Selecting Claude, Codex, Pi, or a custom engine does not by itself resolve deployment/service compatibility.
Consult engine contracts and authentication for the selected provider’s requirements. The tracking issue records this confirmation gap. The AWF owner request covers firewall applicability, not gh-aw product support. Component versions and validation evidence Section titled “Component versions and validation evidence” Record the compiler version, selected engine version/provider/model, MCP gateway and server image digests, AWF version/images, Actions runner version, Docker/Compose versions, GitHub deployment/release, and (for ARC) chart, Kubernetes, and pod configuration when validating a deployment.
The generated .lock.yml records the compiled pins; upgrading the CLI alone does not update an already compiled workflow. Component or feature Prerequisite and scope Evidence GHES artifact actions Compatibility mode selects upload-artifact@v3.2.2 and download-artifact@v3.1.0 . Their Node.js 24 runtime requires Actions Runner 2.327.1+ ; this is an action-runtime requirement, not a GHES product floor. Pin selection , generated artifact tests , and the upload / download action requirements.
GHES cache syntax Compatibility mode omits compiler-generated cache-mode ; the server must independently support the remaining Actions syntax and cache actions. Cache-mode compiler tests and the GitHub.com-only announcement below. ARC/DinD fixes The walkthrough’s historical feature floors are gh-aw v0.82.8 and AWF v0.27.22 . The narrower compiler startup gate requires AWF v0.27.20+ for sysroot/chroot mount fixes; neither is certification of every newer release or an ARC/GHES combination.
ARC required versions and compiler validation . AWF and MCP gateway pins This revision defaults to AWF v0.29.7 and MCP gateway v0.5.4 . Match documentation/schema to the version in your lock file, including overrides. Compiler version constants . Docker and Compose AWF documents Docker Engine 20.10+ and Compose v2.0+ installation baselines. Docker must be accessible to the runner and gateway; these baselines are not an exact-version CI matrix.
AWF version prerequisites . Copilot engine Requires applicable licensing, policy authorization, inference credentials, and connectivity to the deployment’s actual Copilot endpoint. Runner-registration credentials do not authorize inference. Copilot authentication and GHES prerequisites . Optional runtimes Cloud Hypervisor is preview and limited to GitHub-hosted Ubuntu x86_64 KVM runners, not self-hosted/ARC. NVX is preview, requires AWF v0.28.49+ , explicit provisioning/attestation and Linux x86_64 KVM, and rejects ARC/DinD.
Runtime restrictions and AWF optional runtimes . The compiler’s artifact integration tests generate and inspect YAML; they do not run on a GHES appliance. AWF’s CI matrix distinguishes hosted Linux build/unit/live Docker checks from the provider-free live split-DinD harness . These are configured checks, not a claim that every run passed. They do not establish live GHES, data-residency tenant, or Kubernetes ARC validation.
ARC filesystem and AWF configuration scope Section titled “ARC filesystem and AWF configuration scope” For compiled workflows, runner.topology: arc-dind enables compiler-managed staging; runtime handling also probes a tcp:// DOCKER_HOST . The runner and daemon must share the work root at compatible absolute paths. Workspace, tool cache, home/output state, and mounts must be daemon-visible; the runner’s private /usr , /lib , /bin , and /sbin require sysroot staging.
Rootless runner installation does not remove the DinD sidecar’s privileged: true requirement. See the ARC walkthrough and self-hosted host isolation checklist . The pinned AWF published schema and source schema describe standalone AWF JSON, not gh-aw frontmatter. The current AWF applicability notices were merged after v0.29.7 ; links to AWF main provide current scope guidance, while these pinned schemas describe the compiler’s default release.
Standalone AWF field Meaning at the pinned release runner.topology standard or arc-dind ; ARC enables sysroot staging and tool-cache warnings, not every other setting. runner.sysrootImage Optional ARC sysroot image override; defaults to the release-tagged build-tools image staged into a named volume. container.dockerHost Docker daemon URI; uses DOCKER_HOST when omitted. container.dockerHostPathPrefix Bind-source path translation for layouts that need it; intentionally omitted by gh
The rest of this page is on the live site.