Respondedorbot

An AI Telegram bot with an Argentine personality.

It streams replies, remembers conversations, understands media, tracks markets, manages AI credits, and runs scheduled tasks.

Try it: t.me/respondedorbot

What it can do

• Chat with AI, memory, web search, tools, and provider fallback
• Transcribe audio or YouTube captions and describe images or GIFs
• Summarize YouTube videos from their existing captions
• Summarize conversations
• Show crypto, market, dollar, BCRA, weather, and Polymarket data
• Manage Telegram Stars, AI credits, transfers, and charge history
• Create recurring or one-time scheduled tasks
• Repair supported links and handle localized Telegram commands

Run it locally

1. Install the requirements

• Rust 1.98
• PostgreSQL
• Redis Stack with RediSearch
• FFmpeg

2. Create the configuration

cp .env.example .env

Edit .env and set these values:

Variable	What it is for
TELEGRAM_TOKEN	Telegram bot token from BotFather
TELEGRAM_USERNAME	Bot username, with or without @
SUPABASE_POSTGRES_URL	PostgreSQL database URL
COINMARKETCAP_KEY	Crypto market data
OPENROUTER_API_KEY	AI chat, vision, summaries, and fallback

The bot also needs a personality prompt. Choose one option:

• Set BOT_SYSTEM_PROMPT in .env.
• Create workspace/SOUL.md and, optionally, workspace/RULES.md.

Redis uses localhost:6379 by default. See .env.example for optional providers, monitoring, polling, and maintenance settings.

3. Build and check the configuration

cargo build --locked --release -p botd

set -a
. ./.env
set +a

./target/release/botd --check-config

4. Start the bot

./target/release/botd

Stop it with Ctrl+C. The bot waits for background work to finish before it exits.

Important

For Supabase, use the session pooler on port 5432 with sslmode=require. Do not use the transaction pooler on port 6543.

Main commands

AI and media

Command	Purpose
/ask, /pregunta, /che, /gordo	Chat with AI
/resumen, /summary, /tldr	Summarize the conversation
/transcribe, /transcript, /describe	Transcribe audio or YouTube captions; describe images or GIFs

Data

Command	Purpose
/p, /prices, /precios	Crypto and traditional markets
/c, /cripto, /criptos, /crypto, /cryptos	Crypto prices and conversions
/clima, /weather	Current weather
/dolar, /dollar, /usd	Dollar rates
/s, /accion, /acciones, /stock, /stocks	Stock prices
/petroleo, /oil	Oil prices
/eleccion, /elections	Polymarket elections
/bcra, /variables	BCRA variables
/devo, /rulo	Arbitrage calculations
/powerlaw, /rainbow, /satoshi	Bitcoin reference models

Bot tools

Command	Purpose
/config, /settings	Chat settings
/language, /idioma	Language settings
/topup, /balance	Add or check AI credits
/charges, /history, /gastos	Credit history
/transfer	Move credits to a group
/tarea, /task, /tareas, /tasks	Manage scheduled tasks
/random, /convertbase, /comando, /time	Utilities
/gm, /gn, /help, /instance	Greetings and bot information

/p and its aliases resolve cryptocurrencies, stocks, company names, and tokens. /c keeps lookup restricted to crypto. Canonical assets take priority over DEX namesakes: /c bitcoin resolves BTC and /p apple resolves AAPL. Use stock: or crypto: to disambiguate. A single asset gets a chart; comma-separated lists such as /p btc,timba combine market and token quotes. Bare /c shows Bitcoin; bare /p, top-N lists, stablecoin lists, and conversion options retain their list behavior.

Full Solana/EVM addresses and $ticker messages share the command resolver. Addresses preserve case and pin the token identity; symbol searches require an exact match. DexScreener and pump.fun supply token cards. Missing chart history or photo delivery falls back to the available quote/card text, and missing metrics are shown as N/A. Pump.fun bonding-curve tokens use pump.fun’s candle feed for explicit chart ranges. When only an older trade is available, the chart shows its price across the window and labels it “last available trade price”.

Chart ranges use h (hours), d (days), w (weeks), m or mo (30-day months), and y (365-day years), for example /c bitcoin 1m, /c bitcoin 7d, /p apple 1y, or /s AAPL 5y. Candle granularity is selected automatically. Charts label the dates actually returned by the provider; newly created tokens and unavailable history cannot fill an older requested range. For a single cryptocurrency or stock with an explicit range, the caption uses the chart provider’s current quote and percentage change from the first available candle’s opening price, labeled with that range. Without an explicit range, the caption keeps the default daily change.

Test it

Run the same checks used by pull requests:

cargo fmt --all -- --check
cargo check --locked --workspace --all-targets --all-features
cargo clippy --locked --workspace --all-targets --all-features -- -D warnings
cargo test --locked --workspace --all-features

Integration tests use synthetic data. Set TEST_REDIS_URL, TEST_POSTGRES_URL, and TEST_DATABASE_URL to include Redis Stack and PostgreSQL tests.

Coverage requirements:

• bot-core: 95%
• bot-adapters: 95%
• botd: 95%

More detail: Testing

How the code is organized

botd          Starts the app and connects all services
  |
  +-- bot-adapters   Telegram, HTTP, Redis, PostgreSQL, AI, and media
        |
        +-- bot-core   Parsing, routing, state machines, and domain rules

Dependencies point toward bot-core. External payloads are decoded in bot-adapters, while deterministic behavior stays in bot-core.

Path	Contents
crates/bot-core	Domain behavior and state machines
crates/bot-adapters	External service implementations
crates/botd	Executable and composition root
docs	Architecture, persistence, billing, and testing
quadlets, systemd	Deployment and maintenance units
Containerfile	Rust-only production image

Read more: Architecture · Billing · Persistence

Deploy with Podman

Show deployment commands

podman build --tag respondedorbot:local .

mkdir -p ~/.config/containers/systemd
mkdir -p ~/.config/systemd/user
mkdir -p ~/respondedorbot/workspace

cp quadlets/* ~/.config/containers/systemd/
cp systemd/respondedorbot-maintenance.* ~/.config/systemd/user/
cp systemd/respondedorbot-podman-prune.* ~/.config/systemd/user/
cp .env.example ~/respondedorbot/.env

podman run --rm --env-file ~/respondedorbot/.env \
  -v ~/respondedorbot/workspace:/app/workspace:ro \
  respondedorbot:local /usr/local/bin/botd --check-config

systemctl --user daemon-reload
systemctl --user enable --now respondedorbot-maintenance.timer
systemctl --user enable --now respondedorbot-podman-prune.timer
systemctl --user start respondedorbot-redis.service
systemctl --user start respondedorbot.service

Before starting, edit ~/respondedorbot/.env and add the personality files to ~/respondedorbot/workspace, or set BOT_SYSTEM_PROMPT.

The runtime image contains botd, FFmpeg, and native shared libraries. CI publishes latest and immutable sha-<full-commit-sha> images.

To roll back, pin the Quadlet Image= setting to a verified SHA tag, reload the user units, and restart the service.

Warning

Never run two pollers with the same Telegram token.