Using the agent
SILV runs on Claude Opus 4.8 with adaptive thinking and an agentic tool loop — you describe an outcome in plain English, and it chains the tools below to get there. You never call tools yourself: say “reply to anything mentioning support” and SILV sets up the monitor for you.
Tool reference
Everything the agent can do. Platform tools appear only when that platform is connected.
| tool | platform | what it does |
|---|---|---|
discord_list_channels | Discord | Lists the servers and channels the bot can see. |
discord_read_messages | Discord | Fetches up to 100 recent messages from a channel. |
discord_send_message | Discord | Sends a message to a channel. |
discord_reply | Discord | Posts a threaded reply to a specific message. |
telegram_read_messages | Telegram | Reads from the live in-memory buffer of messages received since the bot connected (last 500 kept — bots can’t fetch older history). |
telegram_send_message | Telegram | Sends a message to a numeric chat id, or @channelusername for channels the bot administers. |
telegram_reply | Telegram | Replies to a specific Telegram message. |
create_monitor | Both | Watches incoming messages for a match pattern and runs your instructions automatically when one hits. |
list_monitors | Both | Lists the currently active monitors. |
delete_monitor | Both | Removes a monitor. |
create_scheduled_task | Both | Runs instructions on a schedule — daily at HH:MM (server-local) or every N minutes. |
list_scheduled_tasks | Both | Lists the currently active scheduled tasks. |
delete_scheduled_task | Both | Removes a scheduled task. |
Monitors
A monitor watches every incoming message on Discord, Telegram, or both. When a message matches, SILV runs your instructions automatically in a one-shot agent run — it can reply, escalate, cross-post, whatever you told it to do.
Match syntax — a case-insensitive substring (e.g. support) or a regex pattern with flags (e.g. /outage|down/i).
Optional chat filter — restrict a monitor to a single channel or chat instead of everything the bot can see.
No confirmation — automated runs act immediately without asking you first. Word the instructions carefully, and test in a quiet channel before pointing a monitor at a busy one.
Scheduled tasks
Scheduled tasks run instructions on a timer, in two flavors:
daily
Runs once a day at a fixed HH:MM in the server's local time zone. Good for digests and reports.
interval
Runs every N minutes. Good for periodic checks — remember each run costs API calls, so pick the slowest interval that works.
Both monitors and schedules work even with only one platform connected, and both show up in the dashboard's Automations sidebar with a live activity log.
Good example prompts
read
> summarize the last 100 messages in #announcements
monitors
> reply to anything in Discord that mentions 'bug' — ask for repro steps and point them to the support channel
monitors
> watch the Telegram group for /urgent messages and forward them to #alerts on Discord
schedules
> every morning at 9:00, post yesterday's highlights from #general to my Telegram channel
schedules
> every 30 minutes, check #status for error reports and ping me if anything looks broken
manage
> list my active monitors and delete the one watching for 'gm'
Limits & behavior
No built-in auth — SILV AI is meant for local, self-hosted use. Add authentication before exposing it on the public internet. Read the security page →
Ready to try it? Connect your keys at /console — or start from the getting started guide →