Frequently asked questions
Everything people usually ask before connecting their first bot. If it’s not covered here, the docs go deeper.
SILV AI is a free, self-hosted web app that runs an AI agent (“SILV”) on your own Anthropic API key. Connect an optional Discord bot and/or Telegram bot, and SILV can read channels, send messages, reply in threads, and run automations like keyword monitors and scheduled tasks — all from a chat dashboard at /console.
Your pick. With an Anthropic key, SILV defaults to Claude Opus 4.8 but the connect screen's dropdown offers the whole family — Claude Fable 5, Sonnet 5, Opus 4.7/4.6, Sonnet 4.6, Haiku 4.5, or any custom model id. Prefer OpenRouter? Switch the provider toggle and use any tool-calling model slug. Either way there is no SILV-hosted model — every request goes straight from your machine to the provider, driving an agentic tool loop of up to 25 tool steps per turn.
No. Either one is enough, or both if you want. Monitors and scheduled tasks work with whichever platforms you have connected — a monitor set to platform: both simply watches everything that is live.
Yes — you bring your own Anthropic API key, and Anthropic bills you directly for whatever the agent uses. SILV AI itself is free and self-hosted; it adds nothing on top. See the API key guide for setup.
Create a bot in the Discord developer portal, enable the Message Content privileged intent, invite the bot to your server, then paste the bot token at /console. The full walkthrough is in the Discord guide.
Just ask in plain English. Tell SILV “reply to anything mentioning support” or “post a summary every morning at 9” and it creates the monitor or scheduled task for you. Active automations show up in the dashboard’s Automations sidebar with a live activity log, and you can ask SILV to list or delete them anytime.
No. Your Anthropic key and bot tokens are held in server memory only, scoped to your browser session, for a maximum of 12 hours. Nothing is ever written to disk or a database. Disconnecting — or restarting the server — wipes the keys, tears down the bots, and clears all monitors and schedules. More detail on the security page.
Everything resets. The Discord and Telegram bots disconnect, your keys are wiped from memory, and all monitors and scheduled tasks are cleared. When you reconnect you start with a clean session and set up automations again.
Not as-is. SILV AI has no built-in authentication — it is designed for local or self-hosted use. Anyone who can reach the page can use your connected keys and bots. If you must expose it, put it behind your own auth layer, a reverse proxy with a login, or a VPN first.
It’s a Telegram Bot API limitation: bots cannot fetch chat history. SILV keeps a live in-memory buffer of messages received after the bot connects (the last 500), and telegram_read_messages reads from that buffer. Anything sent before you connected is invisible to the bot.
Your bot needs the Message Content privileged intent. In the Discord developer portal, open your application → Bot → Privileged Gateway Intents, enable Message Content Intent, save, and reconnect. The Discord guide walks through it.
Yes — while your session is live. Monitors trigger an automatic one-shot agent run on every matching message (substring or regex, with an optional channel filter), and scheduled tasks run daily or at fixed intervals. They act without asking for confirmation, so treat them as autonomous. If the session expires or the server stops, automations stop with it.
Only one chat turn runs at a time — a busy guard blocks a new turn while the previous one is still working through its tool loop. Wait for the current turn to finish and send again. Automations are unaffected; they run in the background on their own transcripts.