YHITL Forjal Alpha

YOUR HARDWARE IN THE LOOP

Your hardware.
Your local AI.

Codex and Claude Code keep planning and reviewing. Forjal runs the work they hand off on the machine in front of you.

Download Forjal Loading release… All platforms and checksums macOS · Windows ARM64 · Windows x64

Apple Silicon · Snapdragon X · Intel and AMD

BEFORE YOU INSTALL

These builds are not signed yet.

Forjal alpha builds carry no Developer ID on macOS and no Authenticode certificate on Windows. Both systems will tell you the app comes from an unidentified developer and ask you to confirm before it runs. That prompt is expected — it is what an unsigned build looks like, not a sign that something went wrong. Signing certificates are being issued and will land before the stable channel. Until then, every artifact ships with the SHA-256 of the exact file that was built, so you can check what you downloaded.

FIRST LAUNCH

One extra confirmation, once.

MACOS

Allow it in Privacy & Security

  1. Open the DMG and drag YHITL Forjal to Applications.
  2. Open it once from Applications. macOS blocks it and says it cannot verify the developer.
  3. Go to System Settings → Privacy & Security, scroll to Security, and choose Open Anyway.
  4. Confirm with Open. macOS remembers your choice.
WINDOWS

Confirm past SmartScreen

  1. Run the installer. SmartScreen shows Windows protected your PC.
  2. Choose More info.
  3. Choose Run anyway.
  4. The installer is per-user. It never asks for administrator rights and installs only for your account.

If the app disappears after installing

An unsigned installer carrying an embedded Python runtime is a common false positive. If your shortcut reports that YHITL Forjal.exe was changed or moved, antivirus software most likely quarantined it after the install finished. Add the install directory as an exclusion, then install again: 

Add-MpPreference -ExclusionPath "$env:LOCALAPPDATA\Programs\YHITL Forjal"

This is a consequence of shipping without a signature, and it goes away once these builds are signed.

VERIFY YOUR DOWNLOAD

Check the file against its checksum.

One command prints the SHA-256 of the file on your disk. If it matches the value published next to your platform above, the file is byte-for-byte what the build produced.

MACOS 
shasum -a 256 ~/Downloads/<file>
WINDOWS POWERSHELL 
Get-FileHash .\<file> -Algorithm SHA256

WHAT ALPHA MEANS HERE

What is settled, and what is not.

  • The delegation contract can still change

    Tool names, model identifiers and the shape of what Forjal reports back to your agent may change between alpha releases.

  • Models are not bundled

    The installer carries the app and its runtime. You pick a model on first run and Forjal downloads it then — nothing is fetched before you ask.

  • Acceleration depends on your hardware

    Each build targets one cohort: MLX on Apple Silicon, the Hexagon NPU on Snapdragon X, Foundry Local on Intel and AMD. Forjal tells you what it found and never substitutes one for another in silence.

  • Updates are in-app and opt-in

    Forjal checks this site for a newer alpha on launch and every six hours. It downloads and installs only when you say so.

FIRST RUN

From this page to your first local generation.

  1. 01

    Install

    Open the installer for your platform and follow your system's flow.

  2. 02

    See your hardware

    Forjal reports the architecture and execution providers it found.

  3. 03

    Pick a model

    Choose from the catalog and Forjal prepares it for your machine.

  4. 04

    Connect your agent

    Point Codex or Claude Code at the MCP bridge and delegate your first task.