Aevum Cadence AI

Installation

Linux is first. Download the desktop app, hatch an assistant, name it yourself. There is no seeded house persona and no cloud signup. Bring your own model keys.

Canonical URL: /docs/getting-started/installation

What you need

Get the files from the home page.

AppImage

  1. Download the AppImage from /download/linux-appimage (the live version comes from the update feed).
  2. Make it executable and launch it: 
    chmod +x Cadence-*-x86_64.AppImage
./Cadence-*-x86_64.AppImage
  3. Hatch an assistant. Name it yourself.
  4. Add a model provider (OpenAI-compatible URL plus key, or a local Hive). Then say hi.

Optional: verify the download with the public signing key. 

curl -fsSL https://www.aevumcadence.ai/keys/aevumcadence-linux-signing.gpg | gpg --import
gpg --verify Cadence-*-x86_64.AppImage.asc Cadence-*-x86_64.AppImage

Install with apt

The key file is ASCII armor. Apt signed-by=*.gpg needs a binary keyring, so dearmor it first. Package name is cadence. 

curl -fsSL https://www.aevumcadence.ai/keys/aevumcadence-linux-signing.gpg \
  | gpg --dearmor \
  | sudo tee /usr/share/keyrings/aevumcadence-linux.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/aevumcadence-linux.gpg] https://releases.aevumcadence.ai/apt stable main" \
  | sudo tee /etc/apt/sources.list.d/aevumcadence.list
sudo apt update
sudo apt install cadence

Or install a downloaded .deb without the repo: 

sudo apt install ./Cadence-*-amd64.deb

Apt repo: releases.aevumcadence.ai/apt.

Hatch

Launch Aevum Cadence AI. Hatch a new assistant. Give it a name. The blank assistant you name is the product. There is no seeded persona and no hosted browser hatch in 0.1.

Next: Quick start.

Model provider

You bring the brain. Configure an OpenAI-compatible endpoint (hosted or a local Hive) and store the key in the credential store. Do not paste secrets into chat.

Cadence does not ship a billed cloud model profile in 0.1. There is no Cadence Cloud signup.

CLI on PATH

After the first packaged launch, the cadence command is installed onto your user PATH (also File → Install cadence Command). AppImage does not put a binary in /usr/bin. 

which cadence
# expect: $HOME/.local/bin/cadence
cadence --help

If which cadence fails, open a new terminal, or add $HOME/.local/bin to your PATH.

What gets installed

The assistant lives on your machine. There is no encrypted Cadence Cloud account in 0.1.

Instance workspace
~/.local/share/cadence/assistants/<id>/. Identity, soul, memory, SQLite, and skills live under that instance. A legacy fallback is ~/.cadence/workspace/.
Electron data and bundled CLI
~/.config/@aevumcadence/linux. Session logs are under logs/ there. The assistant binary is bundled with the app.
User PATH launcher
~/.local/bin/cadence, owned by Cadence, forwarding to the versioned runtime under Electron userData cli/<version>/.

Workspace files are plain text you can open and edit. See The workspace.

Updates

On the bundled Linux desktop, use Help → Check for Updates, or install a new AppImage / .deb.

AppImage auto-update uses the public feed at releases.aevumcadence.ai. Deb installs stay on apt: 

sudo apt install --only-upgrade cadence

Do not run cadence upgrade on the bundled desktop app. That command is the npm-distributed CLI path. Packed Linux has no npm runtime, so it fails. Help → Check for Updates is the right path.

Mobile and other desktops

iPhone, Android, Windows, and macOS clients are later. Linux is the 0.1 ship target. Do not use a third-party App Store listing as an Aevum Cadence AI download.

Permissions

Cadence does not ask for every host permission up front. Sensitive actions (files outside the workspace, shell, sending mail) stop and ask in the app. You Allow or Deny. See The permissions model.

Definitions

Assistant
A named instance you hatch. Own identity, memory, and skills.
Guardian
The person who creates and is responsible for the assistant.
Hatch
Creating a new assistant. Not sign up.
Skill
A durable capability: a folder with a recipe the assistant follows.

More terms: Glossary.