The Memory Tree

Every chat becomes a vault you own

Iva doesn't just answer, it files. Voice notes, photos, forwarded posts and decisions become plain-markdown cards it actually remembers, on your server, in an Obsidian-compatible vault.

How Iva remembers: a leaf is a day, branches are weeks and months, tree rings are years around CORE.md

How Iva remembersDaily logs, distilled nightly

Leaves: The word-for-word transcript of each day, Iva's replies included. Nothing is paraphrased on arrival.daily/YYYY-MM-DD.md
Branches: Summaries folded upward every night at 04:00: day → week → month → year. Facts that change get rewritten, not piled up.summaries/daily/ · weekly/ · monthly/ · yearly/
Trunk: CORE.md, a distilled profile under 1,200 characters that rides in every prompt, plus typed cards: contacts, projects, decisions, ideas. Iva knows you before it searches anything.CORE.md · cards/
Search: BM25 on Node's built-in SQLite plus a link-graph rerank, any language; one key turns on the vector hybrid. Full architecture.

How it works

No domain, no webhook, no middleman

The bridge long-polls Telegram, so any small VPS is enough. Voice, text, photos and PDFs fly in; memory, schedules, search, web and Google Workspace answer back. Everything on your box.

How Iva works: voice, text, photos and PDFs fly from Telegram into the willow-tree agent, wired to memory, nightly rollup, cron, reminders, search, web, workspace and docs

Telegram → agent → vaultRuns as two systemd services

What people ask Iva

"What did we agree with client X about the last shipment?"
Found in seconds, months later

"A five-minute voice note from the car."
A task list, a draft email, a meeting card

"Make a quote from this price list and send it to the client."
A finished Google Doc, link in the chat

What people ask Iva: eight everyday requests, from a voice note turned into tasks to research with sources and a bedtime story that continues tomorrow

Eight of many25+ real scenarios →

Features

A full assistant, one chat away

Voice: Voice, audio and video notes transcribed with Deepgram nova-3; auto-detects English, Russian, Uzbek.
Vision: Photos described by your provider's own vision model. No extra key, no extra bill.
Rich replies: Tables, checklists, collapsible blocks and formulas render natively in Telegram.
Documents: Send a PDF, DOCX or XLSX. Iva reads it, answers on its content and can file it into the vault, searchable by meaning.
Personal CRM: Who your people are, what you agreed, when to follow up. Decision cards keep the why.
Web search: Four pluggable providers: Tavily, Exa, Parallel or Brave. The key goes in right in the chat.
Google Workspace: Gmail, Calendar, Drive, Sheets, Docs and Tasks from chat. Installed for you, with a guided key setup in the conversation.
Tasks & digest: Priorities, due dates, reminders and a morning digest that greets you before coffee.
Skills & MCP: Drop one markdown file to add a procedure, or connect any MCP server; keys stay in .env.
Your model: Four providers to choose from: OpenCode Go, Ollama Cloud, OpenRouter, or your own ChatGPT subscription. Your keys, your choice.
Self-updating: A quiet daily check, then one-tap Update in Telegram, staged, with rollback. /usage reports every token for free.

Userbot

A secretary inside Telegram

Connect the userbot and Iva works from your personal account like a secretary: reads the group chats you never keep up with, folds them into summaries, catches the messages that actually need you, and replies as you.

Your secretary inside Telegram: the userbot reads group chats from your own account, collects summaries and replies as you, guarded by a server-enforced anti-ban guardrail

Your own account, working for youGuardrail enforced server-side

All of Telegram: Groups, channels, unreads, search and the full history of your personal account.
Onboarding in chat: Tell the bot to connect your Telegram, scan a QR. No terminal.
Anti-ban guardrail: FloodWait compliance, randomized pacing and a circuit-breaker, enforced on the server, not asked for in a prompt.
Read-only mode: One .env switch and Iva can read and search but physically cannot send.

Security

Guarded in, guarded out

You'll forward Iva things from the outside: links, web pages, other people's messages. Web pages, search results, voice transcripts, captions and the vision model's description reach the model only through a prompt-injection sanitizer; a forwarded text message is tagged with a warning instead. Every reply passes a secret-redaction gate, and the allowlist fails closed: an empty list answers nobody. Your memory is a private git repo you own. Gate internals.

Untrusted input from Telegram and the web passes the security gate: corrupted messages drop into the reject tray, only clean context reaches the vault

Untrusted in, clean outLinks, web pages and forwards pass the gate first

Install

Up and running in five minutes

Get a tokenMessage @BotFather in Telegram, create a bot, copy the token.
Run one commandAny Ubuntu/Debian box: a fresh VPS or your own machine. The installer asks, you answer.
Message your botThe wizard picks your Telegram ID out of that message, finishes setup, and Iva confirms in the chat that it's live.

curl -fsSL
              https://raw.githubusercontent.com/smixs/iva-agent/main/install.sh
              | bash

IVA