Early preview
Compiler questions and answers
What the Compiler is, which platforms the early preview covers, how access works, and how to reach us.
About the Compiler
What is the Compiler?
The Compiler builds programs written in the Open Engineering Language, a programming language for building AI agents as reliable, native software. You write agents, their prompts, tools and workflows as typed code, and the Compiler builds them into self-contained native programs.
Which platforms does it build for?
The Compiler is designed to build for Linux, macOS, Windows, containers and microcontroller boards from one language. In the early preview Linux comes first; the other platforms are being qualified.
Do I need to install anything else?
Desktop and server programs written in the language alone need nothing else installed: there is no interpreter or virtual machine to ship. Functions you write in other languages are built and run with your own toolchains.
Can I use my existing programs?
Yes, by design. You call your existing Python, JavaScript, Java or .NET programs and shell commands as typed tools, with runtimes you provide. Your application can also hold private functions written in other languages, with typed signatures in the language, pinned by version.
Access
How do I get Compiler 1.0.0?
Compiler 1.0.0 is in early preview and no download is published. Early preview — message us for access: write to hello@openeng.ai with the platform you build on and what you plan to build, and OpenEng Labs replies by e-mail.
Where is everything?
Access starts at openeng.ai/compiler/downloads. The documentation is at docs.openeng.ai, the package registry at pack.openeng.ai, and the record of every release at releases.openeng.ai.
Packages and releases
Who publishes packages?
Only OpenEng Labs publishes to the official registry; every version is signed, and a published version never changes. In the early preview no official package has been published yet. You can build private packages and host them yourself.
What are packages written in?
Every package, from OpenEng Labs or from you, is written in the Open Engineering Language and ships in compiled, verified form, with no bundled native code and no install scripts.
Are releases signed?
The Compiler is designed to ship as a signed, reproducible release with a software bill of materials. In the early preview no release file is published.
Security and support
How do I report a security issue?
Write to hello@openeng.ai with what you found, the Compiler version and platform you use, and the steps or the smallest example that shows it. Keep the issue private until a fix is published or we have agreed with you to make it public.
What should I leave out of a report?
Leave passwords, API keys, tokens, private prompts and business data out of every report and support request. Remove them from logs and examples first. OpenEng Labs never asks for them.
How do I get help?
Support is by e-mail: write to hello@openeng.ai with the Compiler version, your platform, what you did and what happened.
Resources
More on the Compiler
Compiler overview
What the Compiler is, how you write, check, build and run a program, and where programs run.
Features
The designed scope by area: language, agents, models, services, tooling, deployment and devices.
Agents
Agents, nodes and edges as typed source files, with teams, subagents and built-in guardrails.
Packages
The signed official registry, the package families, and private packages you build and host.
Compiler 1.0.0
What the early preview covers today, area by area, and how to follow each update.
Get the Compiler
Early preview access by message, per platform. No public download is published.
Documentation
The language guide, agents, packages, platforms and the command-line reference.
Release notes
The record of every Compiler release, on the releases site.
A question that is not here?
Write to hello@openeng.ai. The same address handles access to the early preview.