Forge is preparing the requested surface and verifying the live route.
Forge is preparing the requested surface and verifying the live route.
The local runtime for your device-powered Forge account. Connect a machine, join your personal compute mesh, and keep account, privacy, limits, and recovery visible.
Version pending publication · Signed installers appear here only after release artifacts and signing proof are verified
Detected: Windows (x64)
ForgeOS binaries are not published yet.
Direct installers are disabled until release artifacts, checksums, signing proof, and publication metadata exist. Until then, use the source/dev local app bootstrap. The account and mesh paths stay visible, but direct installers stay disabled without pretending binaries exist.
Open the local Forge app
powershell -NoProfile -ExecutionPolicy Bypass -Command "iwr https://optimaforge.ai/get/install.ps1 | iex"curl -fsSL https://optimaforge.ai/get/install.sh | shExisting Forge folders are updated safely when they are Git checkouts; otherwise Forge creates a new folder and tells you exactly where it is. After bootstrap runs, it writes an install receipt and local activation passport, creates a launcher, starts Forge, and opens the app UI in your browser.
The source/dev path requires Node.js 22 LTS or newer and opens the full local Forge app/control room, not a terminal-only status page. On Windows it creates a Desktop and Start Menu shortcut; on macOS it can create a Forge.command launcher; on Linux it creates a browser/PWA shortcut through the desktop entry.
The default app URL is http://127.0.0.1:3417; if that port is busy, Forge records the exact local URL in current-app.json. If the browser does not open automatically, run npm run forge:local-first -- dev-app --open or open the URL recorded there.
Direct installers stay disabled until real release artifacts, checksums, and signing proof exist.
Other platforms