Package catalog

Package names on this page are preview naming and may change before launch. The official registry will list every official package and version when it opens.

What every official package shares

• Written in AEL. Every package will ship as compiled, verified AEL, with no bundled native code and no install scripts.
• You will run the outside systems. When a package talks to an outside system, such as a database, a model server, a robot or a quantum computer, it will use that system's own interface, and you will run that system.
• Only what you use will ship. An HTTP-only app will carry no gRPC or WebSocket code, and a GET-only API no POST handlers.
• Added like any other package. ael pack add server/http (command names may change before launch) will add one; see Using packages.

Servers and APIs

server/http, server/grpc, server/websocket, server/mcp

• A console agent will need no server: add server/http and declare routes to make it a REST API, or remove them to go back to console-only. Routes will live in .routes.ael files, a file role that server/http adds, and main will mount them.
• Optional HTTP, gRPC, WebSocket and socket servers will send each reply to the authenticated caller that asked for it.
• An optional package will expose your agents as MCP tools. Calling MCP tools will need no package, because a built-in MCP client will discover and call them; see Tools and MCP.
• Each server will be a separate package: adding server/http will never bring a gRPC, WebSocket or MCP server.

Services and APIs shows one agent served over each of them.

Model providers

You will choose local or cloud models: local model servers, optional packages for major cloud providers, and clients for inference endpoints you run yourself. The model client that will be part of AEL itself is described under Model client, and model bindings and policies under Models and providers.

Caching and messaging

Optional packages will connect agents to streams, caches and message brokers. You will run the cache or broker; the package will speak its protocol.

Running your existing programs as tools

execution/process, execution/shell, execution/terminal, execution/remote, execution/python, execution/javascript, execution/jvm, execution/dotnet

You will call your existing Python, JavaScript, Java or .NET programs, shell commands and operating-system operations as typed tools, with runtimes you provide, locally or on a remote worker. The programs are yours: the package that starts them will be written in AEL, and it will never install a runtime for you. Calling your existing programs shows how, and Files and processes is the reference.

Scientific computing

math/array, math/linalg, math/optimization, math/signal, math/integration, math/autodiff, math/random, math/sparse

Optional packages will provide numerical arrays, complex numbers and linear algebra, and optimization, signal processing, integration and automatic differentiation. Scientific computing describes each package.

Robotics

robotics/transforms, robotics/sensors, robotics/simulation, robotics/kinematics, robotics/dynamics, robotics/planning, robotics/control, robotics/estimation, robotics/mapping, robotics/calibration, robotics/middleware/ros2

• Optional robotics packages will provide typed units, coordinate frames, timestamps and sensor and actuator schemas.
• Robot agents will connect over ROS 2 and DDS, including the DDS-XRCE standard for constrained hardware.
• Optional packages will cover kinematics, dynamics, trajectories, optimal control, localization, mapping, navigation and vision.

Robotics describes each package.

Quantum computing

quantum/circuit, quantum/gates/standard, quantum/sim/statevector, quantum/sim/density-matrix, quantum/sim/stabilizer, quantum/sim/tensor-network, quantum/compile/openqasm, quantum/compile/qir, quantum/algorithms/…, quantum/control/pulse

• Quantum circuits will be typed, with standard and custom gates.
• Quantum simulators (statevector, density-matrix, stabilizer and tensor-network) will state their cost and precision limits.
• Circuits will export to OpenQASM and QIR, with circuit lowering and routing.
• Quantum jobs will run asynchronously on quantum hardware providers, with budgets, cancellation and tenant-scoped credentials.
• Optional packages will cover quantum algorithms, error mitigation and correction, quantum machine learning and quantum chemistry.

Quantum computing describes each package.

Your own connectors

You will write your own connectors for services, models, knowledge sources, transports and log sinks, in AEL. To share one between projects, build it into a package of your own: see Creating a package and Private packages.

For what these families make possible, see Use cases.