AEL 1.0.0 release notes

AEL 1.0.0 is available on request: ask for your download on ael.openeng.ai/download, and OpenEng sends you the build for your platform by e-mail.

What AEL 1.0.0 includes

Language and toolchain

A typed, compiled language for agents, with one command-line tool to create, check, format, build, run and debug projects. The AEL 1.0.0 build for Linux, macOS or Windows comes with target management and a health check, and desktop and server programs written in AEL alone need nothing else installed. Changes to the language or project format come with explicit, reviewable migrations.

Your application can hold private functions written in other languages, with typed AEL signatures, built and run with your own toolchains, pinned by version.

You mark an agent, node or subagent as isolated: it always runs in a sandbox in its own process, outside the shared communication layer, reachable only through the edges you declare and holding only the resources it declares itself. Isolation needs the isolation facilities of Linux and runs only on the Linux target the documentation names for it: on macOS, on Windows, on microcontroller boards, on other Linux targets and on any host without those facilities, an isolated component is refused, never run without isolation.

More in the Language guide, Functions in other languages, Isolated components and the Command-line reference.

Agents and workflows

Prompts as business policy, tools, typed inputs and outputs, multi-agent patterns and subagents, shared budgets, retries, human approvals and runs that resume from a storage point you declare.

An agent spawns subagents at run time: short-lived agents that each do one task, return a typed result to the agent that spawned them and end, leaving nothing running. One agent can spawn more than a hundred subagents for a single request, while only a bounded number run at the same time.

Every edge is a typed, two-way channel: AEL generates the communication between nodes, agents and subagents from your edge declarations, with no client or server code for you to write. The same edge runs in one process, between processes or over the network, as your deployment places it, with no change to your source, and over the network it uses AEL's built-in gRPC-compatible transport with TLS.

An agent, subagent or node declares the memory, skills, knowledge, storage and database it uses, each bound to a package you select, and the check refuses any use it did not declare. A run is durable only when its agent declares a storage point, a storage package you select that keeps the run's state in a directory, in object storage or in an SQL database you run; without one, the run runs to completion and keeps nothing.

A skill is a versioned, reusable bundle of instructions, typed tools and functions that an agent or subagent loads through the skills it declares; its tools run only where the agent's permissions allow, and it adds nothing the agent did not declare.

More in Agents, Subagents, Communication between agents, Bindings and storage and Skills.

Models and knowledge

OpenAI-compatible model clients for local and cloud models, MCP tools, agent-to-agent delegation over A2A, multimodal input and retrieval over your own knowledge (RAG).

More in Models and providers and Tools and MCP.

Services and connections

You turn an agent into an HTTP or gRPC service, react to events and schedules, and call your existing programs as tools.

More in Services and APIs and Calling your existing programs.

Packages

The official registry at pack.ael.openeng.ai, with signed versions published only by OpenEng, and private packages you build and host yourself.

More in Packages.

Platforms

You build for Linux, macOS, Windows, containers and microcontroller boards from one language. Programs run on servers, containers and devices, with nothing to compile or download at startup. Runtimes come in sizes for each class of device, from servers down to coin-cell-class microcontrollers, and a program that does not fit its device's class is refused when you build it.

AEL 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.

Supported targets lists the targets AEL 1.0.0 builds for, and Distributions describes the distributions.

Operations

Time and token usage reports, structured logs, per-agent limits, staged deployments and rollback.

More in Deployment and rollback, Logging and monitoring and Reporting, logs and replay.

Robotics, science and quantum computing

Optional packages for robotics, scientific computing and quantum computing, including ROS 2 support and quantum circuits that export to OpenQASM and QIR.

More in Robotics, Scientific computing and Quantum computing.

Trust

The AEL 1.0.0 release is signed and reproducible, with a software bill of materials. Security reports go to ael@openeng.ai.

Documentation

The full documentation covers every part of AEL 1.0.0: an overview, a first look, the language guide, agents, packages, platforms and deployment, use cases, and the command-line and library reference.

Limits to know about

AEL 1.0.0 has limits worth knowing before you plan around it. They are deliberate, to keep what you write checkable and what your program uses predictable.

• Exact targets only. AEL 1.0.0 builds for the targets on the Supported targets list, and for no other.
• Boards need their makers' flashing tools. You flash and monitor supported boards from the command line, using each board's standard flashing tools. Only desktop and server programs written in AEL alone need nothing else installed.
• Isolation needs its facilities. Isolation needs the isolation facilities of Linux and runs only on the Linux target the documentation names for it: on macOS, on Windows, on microcontroller boards, on other Linux targets and on any host without those facilities, an isolated component is refused, never run without isolation.
• No subagents or network edges on boards. Microcontroller boards create no agent at run time and carry no network transport for edges: the check refuses spawn on them, and an edge never runs over the network there.
• Smaller distributions refuse what they leave out. A smaller distribution refuses a feature it leaves out by naming it, such as a function in another language or a spawn, when you check or build; it never builds your program without that feature.
• Fixed-capacity collections. Memory use is predictable: the built-in collections have a fixed capacity, a full collection gives an explicit result and stays unchanged, and small devices need no heap.
• Small source files. Every source file has a fixed size limit, and a component that needs more room splits its private helpers into extension files. Limits gives the exact numbers.
• Official packages come only from OpenEng. Only OpenEng publishes to the official registry. Your own packages are package files you host yourself: as a release download in your own GitHub or GitLab project, at any https address, or inside your project.

Following releases

Every AEL release is listed on releases.ael.openeng.ai with its version, its release notes and how to get it.

Related

• Release notes: every release, and what each release's notes cover.
• Features: every feature, with a link to its guide.
• FAQ: how to get AEL 1.0.0, platforms, packages, and how to reach the AEL team.