> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agenium.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Install Agenium

> Download Agenium, sign in with your email, and let the onboarding leave your Mac ready to use.

Agenium runs on macOS 14 Sonoma and later. It ships outside the App Store, signed with a Developer ID and notarized by Apple, because the App Store's sandbox would cut it off from the agent tools and session stores it works with.

## Download

**1. Get the disk image**

Download the latest release from [download.agenium.dev](https://download.agenium.dev), a signed, notarized disk image.

**2. Move it to Applications**

Open the disk image and drag **Agenium** onto **Applications**.

**3. Open it**

Open Agenium from Applications. macOS asks once whether to open an app downloaded from the internet; confirm it. After that, Agenium keeps itself up to date through [Update](https://docs.agenium.io/app/updates-and-releases.md).

## Sign in

Agenium runs for a signed-in account with a free seat. Until your Mac is signed in, the window shows only the sign-in.

**1. Enter your email**

Type the email address your Agenium account is registered with.

**2. Enter the code**

Agenium emails you a 6-digit code from `Agenium Labs <noreply@agenium.io>`. It is valid for 10 minutes and for 5 attempts. Type it in.

Each signed-in Mac takes one of your account's seats. Signing in on one more Mac than you have seats frees the seat of the Mac that signed in longest ago; that Mac returns to the sign-in and says it was signed in on another Mac. Signing out frees your seat.

Agenium checks its sign-in at launch and once an hour, and keeps working for up to 7 days without reaching the sign-in service.

## The onboarding

On a Mac where Agenium starts for the first time, it opens through an onboarding that leaves it ready to use. The tools it relies on - the capabilities manager, Claude Code and Codex - install in the background from the moment the app starts, so you never wait on them as a step. A step your Mac already meets shows done and is passed over.

**1. Sign In**

Your Agenium account, as above.

**2. Database**

Agenium keeps your agents, tasks and Inbox in a shared database, and needs one before it opens. Choose one of two:

* **Supabase** (the default): sign in to Supabase in your browser, and Agenium creates a project or connects one you already have, gives it a database role and schema of its own, and turns on its SSL enforcement. You copy no credentials. See [Connect a Supabase database](https://docs.agenium.io/recipes/connect-supabase-database.md).
* **Postgres**: any Postgres of your own, local or remote, by its credentials. You run it and answer for it.

This step cannot be skipped.

**3. Providers**

Sign in to Claude, Codex, or both. Agenium starts each harness's own browser login, so no terminal is needed. At least one is required, since no agent works without one; with one signed in, it becomes the one new sessions start in.

**4. Transcription**

Optionally paste a Deepgram API key for voice input in the composer. You can skip this and add it later in [Settings > Transcription](https://docs.agenium.io/app/settings.md#transcription).

**5. First Agent**

Agenium checks that the tools are ready, or waits for what is still installing, and then creates your first agent, a [Personal Agent](https://docs.agenium.io/first-agent.md), in its standard agents folder. If the database already holds your agents, this step says how many and offers to open Agenium with them or to create a Personal Agent.

## Every launch after that

Agenium opens on a short launch screen. It confirms your sign-in, then checks the capabilities manager, Claude Code and Codex in turn, installing what is missing and updating what is behind through each tool's own installer. Each step settles to a green check with the version it found. A step that cannot complete, such as without a network, says why and does not keep the app from opening.

When your database is on another major version of its schema than this copy of Agenium's tools work with, Agenium shows the **Upgrade** screen before it opens. Nothing moves until you press **Upgrade**: the screen lists what will happen, takes a backup, shows a few progress steps, and on a failure gives the reason, **Try again**, and where the backup and the log are. A database newer than this copy of Agenium asks you to update Agenium instead.

## Common failures

| What you see | Why, and what to do |
| - | - |
| No code arrives | Check the address and your spam folder. The code comes from `noreply@agenium.io`. |
| The code is refused | It is valid for 10 minutes and 5 attempts. Ask for a new one. |
| "The account is not active" | Your account is disabled. Contact Agenium. |
| "Signed in on another Mac" | Another Mac took this seat. Sign in again here, which frees the oldest seat. |
| A launch step shows an error | Usually no network. The app still opens; the step runs again at the next launch. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.