Iva documentation

Iva is a self-hosted Telegram AI assistant with layered memory that turns your messages into an Obsidian-compatible vault.

• use-cases.md — who runs Iva and for what: scenarios for business, work and everyday life
• install.md — one command on a fresh VPS, from curl to the bot’s first message
• configuration.md — every .env variable and the setup wizard
• memory.md — how the vault compounds: transcripts, rollups, cards, search
• security.md — injection screening in, secret redaction out, allowlist fails closed
• providers.md — every external service, with real prices
• deploy.md — systemd services and timers, long polling, updates, backups
• schedules.md — what runs on its own, the fact every run leaves, the agent waking up with it, and what happens when it cannot
• cli.md — Telegram slash commands and the iva CLI
• menu.md — the /menu settings hub: screen map, what applies instantly vs on restart, key intake, character test, memory interview
• reminders.md — how to ask Iva to remind you, one-time and repeating, the minute dispatcher, failed delivery, limits
• extending.md — skills, MCP connections, custom tools
• plugins.md — plugins: what one is, how to install it, how to write your own, and what you risk
• trace.md — the turn journal: what the core records per turn, how to stitch one turn, retention and the content toggle
• faq.md — short answers on cost, models, privacy, Obsidian
• troubleshooting.md — a silent bot, failed timers, provider errors
• CONTEXT.md — the glossary: one concept, one word, and the words the project does not use (Russian only)
• philosophy.md — skill over code, the thin harness, the wheel principle (Russian only)
• adr/ — the decisions that bind the code: what was chosen, why, and what was rejected (Russian only)
• tech-debt.md — known gaps and deferred decisions, tracked in the open
• brand.md — the IVA logo: colors, variants, clear space and what not to do

Документация на русском: ru/