CEX

Documentation / 01

Start with the runtime.

Install the Linux beta, bring a compatible model endpoint, and keep the runtime on your machine.

Before you install

System requirements

The public beta currently targets 64-bit Linux. The desktop package uses Electron and starts CEX's local Python gateway and interface shell on loopback addresses.

Operating systemx86_64 Linux. The Debian package declares GTK 3, NSS, XSS, AT-SPI, libsecret, and related desktop dependencies.
Disk spaceThe current beta is intentionally complete but large. The Debian package reports roughly 5 GB installed; leave extra room for models and workspaces.
Model runtimeBring a compatible model endpoint. Ollama or llama.cpp can be used separately; model serving is not bundled into this beta.
Windows and macOSNo public installers yet. Native build, signing, and verification work remains.
Linux beta · v0.1.0

Install CEX

AppImage

Download the AppImage from the download section, make it executable, then open it.

chmod +x CEX-0.1.0.AppImage && ./CEX-0.1.0.AppImage

Debian package

Download the .deb and let APT install its declared desktop dependencies.

sudo apt install ./cex-desktop_0.1.0_amd64.deb
Beta means beta.

Back up important work, inspect proposed changes, and do not rely on this build as the only copy of critical data.

Bring your own intelligence

Connect a model

CEX is the system around a model, not the model itself. Start a supported local server such as Ollama or llama.cpp, or configure a provider connection with credentials you control.

Automated first-run Ollama setup is not wired yet. If the interface cannot reach your model, confirm the model server is running and that its endpoint matches the connection configured in CEX.

Local by design

Know where your data goes

The packaged beta excludes developer databases and starts with fresh local stores. Runtime memory, workspaces, and configuration remain on your machine by default.

If you deliberately connect a cloud model, connector, or outside tool, the content you send through it is handled by that provider under its own terms. Review permissions before approving an action.

Documentation

Keep going