System Requirements

Updated on Oct 1, 2026

This article describes the device, terminal, storage, and permission requirements for using Forge.

Supported Operating Systems

Forge provides 64-bit builds for the following platforms:

WindowsmacOSLinux

Platform	Architecture	Support level
Windows 11	x86_64	Fully supported
Windows Server 2025	x86_64	Fully supported
Windows Server 2022	x86_64	Supported
Windows 10	x86_64	Community supported
Windows Server 2016-2019	x86_64	Community supported

Platform	Architecture	Support level
macOS on Intel	x86_64	Fully supported
macOS on Apple Silicon	ARM64	Fully supported

Platform	Architecture	Support level
Linux with glibc 2.39 or newer	x86_64	Fully supported
Linux with glibc 2.39 or newer	ARM64	Supported
Linux with glibc 2.28 or newer	x86_64	Supported
Linux with glibc 2.28 or newer	ARM64	Community supported

Linux systems with glibc older than 2.28 cannot use the published Linux binaries. Those systems require a source build linked against the local system libraries.

Terminal Environment

Forge is a command-line application and requires a terminal or command prompt with permission to execute programs and read and write the project workspace.

Windows systems require PowerShell 6 or later. The PowerShell 5.1 version included with some Windows installations is not supported.

Storage and File Permissions

Forge must be able to:

• Read the project files and configuration.
• Create and update the .forge/ directory and its subdirectories.
• Write workflow artifacts, logs, traces, and generated output.
• Read and write the files that an agent is expected to change.
• Access the configured license location when workflow commands run.

The account running Forge should have normal development permissions for the repository. Restrictive permissions, read-only workspaces, network-mounted filesystems with unreliable file locking, or insufficient disk space can interrupt agent monitoring and workflow state persistence.

See Also

• Licensing