The desktop control plane for your whole project.
Overview
Control is where a project is actually worked on. It holds the project dashboard, the workflow surfaces for every part of the pipeline, and the agent conversation. It also starts the local backend the rest of the tools talk to. Everything it does is a command on the same surface the command line and the agents use, so the interface cannot do something that is unreachable any other way.
Where it fits
Aevornix Control is one system in a pipeline. Each stage takes a defined input and hands a defined output to the next.
Four systems in one production path: Control, Orchestrates the project, the workflows and the agents. AevCode, Plans changes, validates them, and rolls them back cleanly when they fail. Design, Produces the images, textures, materials, meshes and animation a change needs. Core, Renders, simulates, edits and runs the project.
Orchestrates the project, the workflows and the agents.
Control decides what needs to happen and calls AevCode to work out how.
Plans changes, validates them, and rolls them back cleanly when they fail.
Validated changes are applied to the project Core builds and runs.
Produces the images, textures, materials, meshes and animation a change needs.
Assets land in the project alongside the change that asked for them.
Renders, simulates, edits and runs the project.
Evidence
Each item names its source and the date it was last checked.
Control was built as a native desktop application with an installer, from the same web surface the in-editor workspace uses. That 0.3.0 installer was withdrawn on 2026-07-27 because it runs only inside a checkout of the engine repository.
Source: Desktop build run producing the Control executable and Windows installer · Verified
