Getting the Compiler
Compiler 1.0.0 is in early preview — message us for access, and OpenEng sends you the build for your platform by email. This page says how to request it, what the build sets up and what else you need.
How to request Compiler 1.0.0
Tell us your name, email address, organization and the platform you want, and OpenEng sends the Compiler 1.0.0 build for that platform to that address.
| Platform | Access |
|---|---|
| Linux | Early preview — message us for access |
| macOS | Early preview — message us for access |
| Windows | Early preview — message us for access |
Compiler 1.0.0 is in early preview and sent by email on request to hello@openeng.ai, as the Compiler downloads page describes; official packages are on pack.openeng.ai, the full documentation on docs.openeng.ai and the record of every release on releases.openeng.ai.
What the build sets up
The Compiler 1.0.0 build for Linux, macOS or Windows sets up the Compiler toolchain: the oel command and what it needs to build for the targets you choose. The Compiler toolchain is self-contained: one install takes your code all the way to a native program.
Compiler 1.0.0 is the full distribution; smaller distributions of the same version leave out components, such as support for other languages or for agents, and refuse a feature they leave out by naming it. Distributions describes them.
The build also comes with target management and a health check:
- target management adds what a target needs, such as a microcontroller board (Setting up a target);
oel doctorreports the toolchain, the installed targets and anything that is missing.
oel doctor
Supported targets lists the exact targets.
What else you need
What else you need depends on what you build:
- Desktop and server programs written in the language alone need nothing else installed. Programs compile straight to self-contained native executables, with no interpreter or virtual machine to run and no second language to install unless you write functions in one.
- Functions in other languages need their toolchains. Your application can hold private functions written in other languages, with typed signatures in the Open Engineering Language, built and run with your own toolchains, pinned by version. You install each toolchain at the version your code pins, where you build and where the program runs. Functions in other languages describes them.
- Microcontroller boards need their makers' flashing tools. You flash and monitor supported boards from the command line with
oel flashandoel monitor, which use each board's standard flashing tools. - Your existing programs need their own runtimes. When an agent calls your existing Python, JavaScript, Java or .NET programs as tools, they run with runtimes you provide, locally or on a remote worker.
- Models are yours to choose. An agent that calls a model needs a model endpoint: a local model server, a major cloud provider, or an inference endpoint you run yourself.
Nothing downloads at startup
Your lock file pins the exact versions you built with, so builds repeat, even offline, and nothing downloads when an app starts.
Next
- A first program shows the first commands.
- The Overview describes what the Compiler and its language are.
- The FAQ answers common questions about getting the Compiler, platforms and packages.