Components
Five components. One engine at the center.
Three interfaces to watch and steer the team, one engine that does the work where your code lives, and central services that connect it to models. Each part carries a card name: Jack, Queen, and King are the interfaces, Deck is the engine, and Dealer runs the central services.
Looking for the AceLM sites, such as the docs or the archive? See the ecosystem.
The product
How the components fit together.
You can close Jack, Queen, or King without stopping the work, because the work lives in Deck. Deck works with Dealer, which provides AceLM's central services, including access to models.
| Name | What it is | What it does |
|---|---|---|
| Jack | CLI | The command-line interface and agent inspector. A client of Deck for work in the terminal. |
| Queen | Desktop UI | A client of Deck for desktop use. |
| King | Web UI | A client for use in a browser. |
| Deck | Local backend and model interaction engine | Runs the model and tool loop where your code lives, runs and records tool work, and serves the interfaces. Written in Rust. |
| Dealer | Main remote server and central services | AceLM's central services, including access to model providers and coordination across machines and users. |
Early access
Pick the seat that suits how you work.
CLI, desktop, or browser: the team and the record are the same. Tell us where you like to work and what you would hand to the team first.