> ## 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.

# Settings

> Every section of Agenium's Settings: database, Coolify, sidebar, sessions, tasks, Claude and Codex, notifications, transcription, voice, language, problems and profile.

Open Settings from the app menu's **Settings…** or ⌘,. It opens in the main window as one long page; a menu of its sections stays to the left and marks the section in view, and pressing a section brings it to the top. Escape or a sidebar section leaves it.

Secrets you type into Settings travel only to the tool that owns them.

## Database

Agenium keeps your agents, tasks, Inbox and its own marks in a shared database. Two tabs offer two ways to get one:

* **Supabase** (the default): connect through Supabase's own sign-in, with no credentials to copy. Agenium creates a project or connects one you have, sets up a database role and schema of its own, and turns on the project's SSL enforcement - saying first, for an existing project, that clients without encryption will stop connecting. 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.

The form holds the machine's database setting, schema included, which Agenium and the capabilities share. A project's own environment file can override it for that project. Agenium reads and writes the setting only through the capabilities manager.

The page also holds:

* **Pool size**, while the database is a Supabase session pooler: the limit the sidebar's Database row measures against, 15 by default.
* **Connections**: how many connections Agenium keeps open for its own reading, 2 by default.

The sidebar's **Database** row shows how full the database's connections are: grey normally, orange from 70% or when a connection idles in a transaction or responses slow, red from 90% or when Agenium cannot connect, naming the cause such as *Pool full*, *Unreachable* or *Auth failed*.

## Coolify

Coolify is the platform where Agenium places resources, such as an agent's server node. Agenium holds one Coolify connection of its own; it belongs to the app, not to any agent.

* **Connect** an existing instance by its address and API token. Agenium validates the token and keeps it in a file of its own, readable only by you.
* **Create instance** takes the IP address of a server your Mac reaches as root over SSH, and starts an [Oracle](https://docs.agenium.io/app/oracle.md) session that installs Coolify there and pairs it with your Mac. See [Connect Coolify and create an instance](https://docs.agenium.io/recipes/connect-coolify-and-create-instance.md).

An agent that works with Coolify as part of its own job, such as a DevOps agent, has a Coolify connection of its own, unrelated to Agenium's.

## Sidebar

A switch per sidebar widget: Claude usage, Codex usage, CPU, Thermal, Memory, Top processes and Database. All are on by default except Thermal and Top processes.

## Sessions

How the [Sessions](https://docs.agenium.io/app/sessions.md) list shows and orders work:

* The **working indicator** and the **watching indicator**, each choice shown animated.
* The list's **order**: latest turn, most recent activity, or started.
* The **agent icon** size on rows: small or large.
* How a session becomes **read**: **Manual** or **On open**.
* The **session text size**, a step larger or smaller than the rest of the interface.
* **Continuing after a restart**: the phrase Agenium sends to the sessions it continues, and a switch that turns continuing off.
* The context share at which an eternal session compacts, 40% by default.

## Tasks

The **agent icon** size on [Tasks](https://docs.agenium.io/app/tasks.md) rows and cards, chosen apart from Sessions.

## Claude and Codex

Each harness has a section of defaults for the sessions Agenium starts. Each opens with its account line - who is signed in and how, a subscription or an API key - with **Sign out** and **Switch account**, or **Sign in** while none is signed in. Signing in goes through the harness's own browser login; Agenium never reads or writes the harness's credentials.

* **Claude**: the mode a new session starts in, **Bypass permissions** unless you choose otherwise.
* **Codex**: the approval choice a new session starts with, **Full access** unless you choose otherwise.

A session continues in the mode it last ran in; the default applies only to new sessions.

## Notifications

For each event, two switches: **Notifications** for macOS and **Telegram**. Mac is on and Telegram off by default.

| Event | When |
| - | - |
| **Session Needs Input** | A session waits for you while Agenium is not in front or another session is on screen. |
| **Task Assigned to You** | A task waits for you. |
| **Task Complete** | A task of one of your agents completes. Silent. |
| **Service Down** | A service on one of an agent's remote nodes is not running. |

An event that needs you plays a sound and stays in Notification Center until it is resolved, when Agenium withdraws it. Clicking a notification brings Agenium forward on its subject. Notifications are local: Agenium raises them only while it runs.

Above the switches, the section shows whether macOS allows Agenium's notifications, with **Turn on** or **Open System Settings** as needed.

### Telegram

Agenium can also send its notifications to Telegram through a bot you create. Paste the bot's token, then bind one chat by sending the bot a one-time code through the start link. Agenium writes only to that chat. The section shows the bound chat, sends a test message, shows the last failed send, and disconnects. A message reads like the macOS notification, names the agent, and is edited rather than deleted once the event is resolved.

## Transcription

Voice input in the composer:

* **Provider**: Deepgram.
* **API key**: validated against Deepgram and kept in a file of Agenium's own, readable only by you. It is the Mac's one Deepgram key, which every capability that transcribes uses too.
* **Model**: the newest general model by default.
* **Language**: **Automatic** by default, which follows a switch of language within one phrase, or one language.
* **Dictation key**: one tap of right Option by default, or right Command, Fn, or none.
* **Key terms**: words to recognise; type one and press Enter, or paste a list.
* **Sounds**: Soft (the default), Tink, Glass, Click, or Off.

## Voice

Voice mode for sessions: the switch that turns it on, the engine - **Gemini Live** or **GPT Live** - with its key, and one voice prompt per engine. The keys are kept in a file of Agenium's own and leave the Mac only for their provider. See [Talk to an agent by voice](https://docs.agenium.io/recipes/talk-to-an-agent-by-voice.md).

## Interface language

English, Russian or Estonian, each named in its own language. The window changes at once; the app menu in the macOS menu bar follows after a relaunch. What people and agents write stays as written.

## Problems

The problems [Oracle](https://docs.agenium.io/app/oracle.md) recorded, kept on the Mac.

## Profile

Who uses Agenium: your name and your account on the rooms homeserver.


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