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

# Capabilities

> The machine's layer of capabilities: install, allow or quarantine, make Global, and manage each one's connections, service and settings.

A capability is a self-contained command-line tool an agent works through, such as a mailbox, Telegram, tasks or memory. The **Capabilities** section is your Mac's layer of them. Every change you make here runs the capability's or the capabilities manager's own command, so Agenium never edits a tool's files behind its back.

For what each capability does, see the [Capabilities tab](https://docs.agenium.io/capabilities/overview.md).

## Installed, allowed, quarantined

A capability is either only in a catalogue or installed on the Mac.

* **Quarantined**: how an installed capability arrives. No agent can use it.
* **Allowed**: agents can use it, once it is switched on for them.
* **Global**: an allowed capability that is on in every agent by default, while any agent can switch it off for itself. A Global capability still reaches a connection only after the agent is granted one.

Installed capabilities show as tiles with their icon, name and description, and a switch in the corner between allowed and quarantined. An allowed one also shows whether the Mac holds a connection for it.

**System capabilities** are the ones every agent is expected to carry, such as tasks, automations, deployment and askproject. Agenium installs them by itself; they arrive allowed and Global.

### Install one

Below the installed capabilities, the **Available** list shows what the catalogue offers that is not on the Mac, each with **Install**. A capability you install arrives quarantined; Agenium enables none by itself and makes no connection. When the catalogue cannot be read, the list says so with the age of what it shows.

Installed capabilities are kept up to date; a quiet toast at the bottom right shows the progress and anything that failed.

Capability states are read when Agenium starts, after a change Agenium makes, and when you press the section's refresh button.

## A capability's page

A capability's page, on the Mac and in an agent's view, heads with its icon, name and an on/off switch, then its description. It holds up to four blocks, each shown only when the capability has it.

### Availability

A choice of **Global** or **Per agent**.

### Setup

What a capability needs once per Mac before any connection, such as the Telegram app's `api_id` and `api_hash`. **Add** stays disabled, with the reason, until it is set. See [Connect a Telegram account](https://docs.agenium.io/recipes/connect-telegram-account.md).

### Connections

Each connection is a tile: a person glyph with a health dot once checked, its name, and its main identifier, such as a mailbox's address. Its actions sit behind its ⋯ menu; pressing it opens a popover with the rest.

* On the **Mac's page**: **Check**, **Relink**, **Edit**, and **Remove**, which asks for confirmation and names the agents granted it. The page lists every connection your database holds for the capability, an agent's own marked with the agent's name, each with which agents use it and whether they read or read and write.
* In an **agent's view**: only the connections granted to that agent, each marked read or read and write, with **Check** and **Make default**.
* **Give access**, in an agent's view, grants one of the shared connections after asking read or read and write. Another agent's own account is never offered.

The last tile adds a connection through the capability's own flow, in a sheet that keeps you in Agenium: a form for one such as Coolify, a QR code for WhatsApp, a QR code and then the two-step password for Telegram. Adding on the capability's page creates a shared connection; adding on an agent's page creates that agent's own. A connection is recorded only once its login succeeds.

### Service

For a capability that runs a service: its state, its verbs as buttons (start, stop, reload, pause, resume, doctor, as the capability declares them), its health checks, and a live tail of its log, with the full log a press away. For an agent with several nodes, **Runs on** moves the service between them.

### Settings

The keys the capability describes, as controls, each showing whether its value is global or the agent's own, with a way to set it for the agent or return it to the global one. Everything else shows as its JSON or TOML text: read first, then **Edit**, a review of what changes key by key, and **Save**, which applies it through the capability's own command and reloads its service. A file changed outside Agenium since you opened it is never overwritten.

Some capabilities show their settings as the things they govern. Telegram's, which belong to each agent, show in four tabs: **Chats**, **Roles**, **Defaults & prompts**, and **JSON**.

## From the command line

Everything here is also reachable from a terminal through the capabilities manager. `capabilities help` gives the manager's full reference, and `<name> help` each capability's.


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