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

# Recipes

> Step-by-step recipes that take Agenium from a starting point to one working outcome, and the template every recipe follows.

A recipe takes you from a starting point to one outcome that works, end to end, in the app. Each one follows the same shape, so you always know where to look.

> [card] [Connect a Supabase database](https://docs.agenium.io/recipes/connect-supabase-database.md)
>
> Give Agenium its shared database through Supabase's own sign-in.

> [card] [Connect Coolify and create an instance](https://docs.agenium.io/recipes/connect-coolify-and-create-instance.md)
>
> Pair an existing Coolify, or install one on a fresh server.

> [card] [Connect a Telegram account](https://docs.agenium.io/recipes/connect-telegram-account.md)
>
> Set up your Telegram app and link an account by QR code.

> [card] [Add a server node and move a service](https://docs.agenium.io/recipes/add-a-server-node-and-move-a-service.md)
>
> Give an agent a server and run one of its services there.

> [card] [Talk to an agent by voice](https://docs.agenium.io/recipes/talk-to-an-agent-by-voice.md)
>
> Dictate into the composer, or hold a voice call with a session.

## The recipe template

Every recipe page has these parts, in this order:

| Part | What it holds |
| - | - |
| Frontmatter | `title`, `sidebarTitle`, `description`, `icon`, and `status` while the recipe is a draft. |
| **Outcome** | One sentence in bold: what works at the end. |
| **What you need** | What must already be true: accounts, keys, a running server, an agent. |
| **Steps in the app** | A `<Steps>` block, one `<Step>` per action, naming the exact controls. |
| **Steps by command line** | Only where a command line path exists. Name the command and point to its own `help`; never copy a capability's command reference into the page. |
| **Check it worked** | What you see when it worked, in the app first. |
| **Common failures** | A table of what you see and what to do. |
| A diagram | Optional, a `mermaid` flowchart where the parts are not obvious. |
| **Related** | Links to the app pages and other recipes. |

## Drafts and verification

A new recipe starts as a draft: its frontmatter carries `status: draft-unverified`, and its top carries a visible note that its steps await verification against the current release. A reviewer walks every step in the current release of Agenium, corrects what differs, and only then removes the field and the note.


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