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

# Telegram Bot

> Run a Telegram bridge for mobile monitoring and agent interaction — `sf telegram --token --daemon --chat-id`.

Use the Telegram bot when a human operator wants mobile access to SimpleFunctions alerts, slash commands, and natural-language follow-up.

## Start

```bash theme={null}
sf telegram --token YOUR_BOTFATHER_TOKEN --daemon
```

Restrict the bot to one chat:

```bash theme={null}
sf telegram --token YOUR_BOTFATHER_TOKEN --chat-id 123456789 --daemon
```

Use environment variables instead of flags:

```bash theme={null}
export TELEGRAM_BOT_TOKEN=YOUR_BOTFATHER_TOKEN
sf telegram --chat-id 123456789 --daemon
```

## Operate

```bash theme={null}
sf telegram --status
sf telegram --stop
```

## Use with runtime

Run Telegram beside the execution runtime or agent:

```bash theme={null}
sf runtime start --smart --daemon
sf telegram --daemon
sf runtime status --json
```

Use this setup when runtime/agent activity should wake a human operator away from the terminal.

## What it is for

| Job               | Use                                                  |
| ----------------- | ---------------------------------------------------- |
| Mobile alerts     | Receive runtime, position, edge, or market alerts.   |
| Quick inspection  | Ask about a market or thesis from a phone.           |
| Operator handoff  | Push important daemon events to a human.             |
| Voice/short notes | Bridge quick operator notes into the agent workflow. |

Do not paste exchange keys into Telegram. Configure credentials through `sf login`, `sf setup`, environment variables, or the cloud runtime setup flow.