AHMEDX
Guide

SILVA MD WhatsApp Bot: Features, Session ID and Deployment Guide

SILVA MD is a third party WhatsApp Multi Device bot project from Silva Tech Inc, published in the open at github.com/SilvaTechB/silva-md-bot and actively maintained. Its README documents an AI assistant called Agent v2 backed by the ch.at service, a protection suite covering calls, deleted messages, links, view once media and group abuse, media downloaders, group management, games and a set of character themes. The repository homepage names its session selector site, which loads today and is where the README session flow begins, and the README recommends the project own Silva Host platform for deployment. This guide is checked against the repository itself: its README, package.json, LICENSE file and repository tree, together with the session and hosting addresses the README prints. Of those addresses, one documented route has broken since the README was written: the fork checker page the Heroku method depends on returns a 404 error today, and the TalkDrove sharing page did not load when checked.

By AHMED X · November 12, 2026 · Last verified November 12, 2026

About

What Is SILVA MD WhatsApp Bot?

What the project is, who builds it, where its code lives, and the shape of the repository a deployer actually downloads. Several unrelated repositories use the Silva MD name; this guide covers only the SilvaTechB project.

SILVA MD is a third party WhatsApp Multi Device bot developed under the Silva Tech Inc project. Its README describes it as a powerful multi device WhatsApp bot and a multifunctional bot with automation, entertainment, AI assistance, media tools and group management. The README credits Silva as creator and lead developer and a contributor under the Sylivanu account as CEO. Its package file describes the bot as built with Node.js and Baileys, names silva.js as its main file and gives its start script as node silva.js.

The project lives in one public repository, SilvaTechB/silva-md-bot, which is not a fork and which was still being updated in the days before this guide was verified. Its tree holds silva.js as the entry point beside index.js, config.js and handler.js, a config.env.example file for the environment configuration, a plugins folder of feature files, a themes folder of theme definitions, a data folder, and deployment files including a Dockerfile, a Procfile, app.json and fly.toml. Several other repositories use the Silva MD name; they are not this project, and nothing from them is merged into this guide.

On licensing, the records agree. The LICENSE file in the repository carries the MIT License text with a copyright line for Silva Tech Nexus, and the GitHub API detects MIT for the repository, so this guide names the MIT License for SILVA MD.

Features

SILVA MD WhatsApp Bot Features

The README documents its features in tables with the exact commands and settings behind them. The cards below follow that documentation: the Agent v2 assistant, the media tools, the protection suite, the status and group automation, the games, the themes, and the encrypted storage the README describes.

Agent v2 AI Assistant

The README presents Agent v2 as the primary Silva assistant, backed by the ch.at service and requiring no API key in its default form. It documents the agent using approved tools for calculations, command discovery, bot status, persistent chat memory, web lookup, weather and the public media downloader, reached through prefix free Silva messages or the .silva, .autopilot, .agent2 and .copilot commands. An AGENT_API_KEY, AGENT_API_URL and AGENT_MODEL can point it at a structured provider instead. The ch.at backend and the encryption described for its memory are the project documented design, presented here as its documentation states them.

Media Downloading

The README media table documents .play for YouTube audio, .ytmp3 and .ytmp4 for YouTube downloads, .tiktok, .instagram and .facebook downloaders, and .download as a universal public downloader for YouTube, TikTok, Instagram, Facebook and X, with an .autodl switch that detects public social links automatically and a .lyrics command beside them. A spotify plugin file also sits in the repository plugins folder.

Protection Suite

The README protection table names nine features with their switches: Anti-Call rejects calls and notifies the owner, Anti-Delete recovers and forwards deleted messages, Anti-Link removes links posted by non admins, Anti-ViewOnce opens and forwards view once media to the owner, and Anti-Fake, Anti-Demote, Anti-Flood, Anti-Spam and Anti-Bot guard the group. Each is controlled by the environment settings or commands the table prints.

Automatic Status Features

Three settings in the README environment table govern statuses: AUTO_STATUS_SEEN for automatically viewing them, AUTO_STATUS_REACT for automatically reacting to them, and AUTO_STATUS_REPLY for automatically replying to them, shipped with the first two on and replies off.

Group Management

The README group table documents .kick and .promote and .demote for membership control, a .warn system that removes a member automatically at three warnings, .tagall for mentioning everyone, .lock and .unlock for who may send messages, .welcome and .goodbye messages, .poll for WhatsApp polls, and join request handling through .approveall and its companion commands.

Games and Entertainment

The README games table documents .rps for Rock Paper Scissors, .hangman, .ttt for Tic Tac Toe, .trivia, .8ball for a Magic 8 Ball answer, and .joke and .quote for random jokes and inspirational quotes.

Text and Utility Tools

The README smart tools table documents .tts for text to speech, .translate, .textmaker for styled text, .weather, .wiki for Wikipedia search, .qr for QR code generation, .calc for calculations, and .imdb for film and series lookups in the media table.

Multiple Themes

The README themes table lists ready made personalities the bot can wear, naming among them Naruto, Gojo, Itachi, Goku, Luffy, Batman and Thanos alongside the default silva theme, changeable through the .settheme command or the THEME setting. The repository themes folder carries the matching theme files.

Encrypted Database Storage

The README documents optional PostgreSQL storage: when DATABASE_URL is configured, selected Agent v2 conversations, user settings and developer contacts are stored in tables the bot encrypts with AES 256 GCM before writing, using the bot session secret as the encryption source. The database is optional and the README says the bot continues running if Postgres is unavailable. This is the project documented design, recorded here as documented.

Commands

SILVA MD WhatsApp Bot Commands

Unlike many bot projects, this README publishes its own command reference, and every command below appears in its tables. The default prefix is a dot, any command can be explained with .help followed by its name, and some commands require owner or group administrator permissions.

Menu and Help

.menu displays the command categories, built from the live plugin registry each time it is requested according to the README. .allmenu shows the complete command directory, .help gives instructions for an individual command, and .alive checks the bot status.

Download Commands

.play searches and downloads YouTube audio. .ytmp3 downloads YouTube audio and .ytmp4 downloads YouTube video. .tiktok downloads TikTok videos, .instagram downloads Instagram content, .facebook downloads Facebook videos, and .download handles supported public media links across the services the README names. .lyrics finds song lyrics.

AI Commands

.silva, .ask and .ai reach the assistant, and .autopilot, .agent2 and .copilot reach Agent v2. The README also documents prefix free AI interaction: a message that begins with the word Silva speaks to the assistant without any prefix at all.

Utility Commands

.weather gives weather information, .translate translates text, .tts converts text to speech, .calc performs calculations, .wiki searches Wikipedia, and .qr generates QR codes.

Group Commands

.kick removes members, .promote and .demote change administrator status, .tagall mentions the group, and .poll creates a WhatsApp poll. The README group table adds the warn system, lock and unlock, welcome and goodbye, and join request commands documented in the features section of this guide.

Fun and Protection Commands

.joke gives a random joke and .quote an inspirational quote. .antispam manages spam protection, .antilink manages link protection and .anticall manages call rejection, matching the protection suite the README tabulates.

Session ID

How to Get a SILVA MD Session ID

The repository homepage names the project session selector, and the README Step 1 section documents the flow on it: choose QR Code or Pairing Code, link WhatsApp, and copy the SESSION_ID shown. The selector page loads today. This section records the documented flow and the README own warning about what a Session ID is worth.

01

Open the Session Selector

The repository homepage field names silva-session-selector.vercel.app. The page loads today and opens with a choice of connection methods for getting the bot running. It is the only session address the project publishes, and it is linked from the repository itself rather than from any third party page.

02

Choose QR Code or Pairing Code

The README Step 1 instructions give the choice directly: choose QR Code or Pairing Code, link your WhatsApp, copy the SESSION_ID shown, and paste it into your host secrets panel. The selector front page renders its options in the browser; the two methods the README names are the two the project documents.

03

For QR: Scan From Linked Devices

Open WhatsApp, navigate to Linked Devices, select Link a Device, and scan the QR code the service displays. Wait for the authentication to complete before moving on.

04

For Pairing Code: Link With Phone Number

Open WhatsApp, navigate to Linked Devices, and select Link with phone number instead. Follow the pairing service instructions and enter the generated code before it expires.

05

Copy the Session ID Exactly

After successful authentication, the service displays your SESSION_ID. Copy the complete value with no added spaces, ready to paste into the SESSION_ID environment variable or the secrets panel of your chosen host.

06

Keep It Private: The README Own Warning

The README Step 1 section prints its warning in bold: never share your Session ID, because it grants full access to your WhatsApp account. Treat the value as the credential it is: never post it in a public repository, a screenshot or a group chat.

Deployment

How to Deploy SILVA MD WhatsApp Bot

The README documents six hosting routes plus a manual installation, each with its own steps, and this section follows them in the README own order. Two of the six have present day problems that are stated in their steps: the Heroku route depends on a fork checker page that returns a 404 error today, and the TalkDrove sharing page did not load when checked.

01

Silva Host: The README Recommended Route

The README marks Silva Host as official, easiest and optimized, and its deploy table links host.silvatech.co.ke with this repository as the template; that site loads today. Log in or create an account, fill in SESSION_ID, OWNER_NUMBER and BOT_NAME, click Deploy, and check the application logs for the Connected to WhatsApp confirmation the README names.

02

Heroku: The Fork Checker Route Is Broken Today

The README Heroku steps are: fork the repository, open silva-md-fork-checker.vercel.app, click Deploy to Heroku, fill in SESSION_ID, OWNER_NUMBER and BOT_NAME, click Deploy App, and confirm Connected to WhatsApp under More, View Logs. The fork checker page was opened again for this guide and returns a 404 error, so the documented button route does not work today even though the steps themselves are fully documented in the README.

03

Railway: Deploy From GitHub

Fork the repository, open Railway, create a new project, and select Deploy from GitHub with your fork. Open the Variables section, add SESSION_ID, OWNER_NUMBER and BOT_NAME, deploy, and check the logs for a successful WhatsApp connection.

04

Koyeb: Set the Documented Run Command

Fork the repository, open Koyeb, select Create App and choose GitHub as the source. Select your fork, set the run command to node silva.js exactly as the README instructs, add SESSION_ID, OWNER_NUMBER and BOT_NAME as environment variables, and complete the deployment, checking the logs afterwards.

05

Replit: Secrets and Run

Open or fork the project in Replit, go to Tools and select Secrets. Add SESSION_ID, OWNER_NUMBER and BOT_NAME, save the secrets, run the application, and check the console for the WhatsApp connection message.

06

TalkDrove: The Sharing Page Did Not Load

The README TalkDrove steps are: open host.talkdrove.com/share-bot/49, select Host This Bot, enter your SESSION_ID and OWNER_NUMBER, and complete the deployment. That sharing page was opened for this guide and did not load, the connection failing outright, so this route is recorded as documented but unverified today.

07

Manual Installation: Node.js 20 or Newer

The README local and VPS section requires Node.js 20 or newer and Git, and the package file engines field agrees on Node 20. Clone the repository, run npm install, copy config.env.example to config.env and fill in your SESSION_ID and OWNER_NUMBER and the rest of your settings, then start the bot with node silva.js.

08

Keep It Running With PM2

The README documents PM2 for continuous running: install it with npm install -g pm2, start the bot with pm2 start silva.js --name silva-md, then pm2 save and pm2 startup so the process returns after a reboot.

Configuration

SILVA MD Configuration Settings

The settings below are taken from the README environment variable tables, which give each setting a default and a description. They are set as secrets on a host or in a local config.env file built from the config.env.example the repository ships.

SESSION_ID

The one required setting in the README essential table: your WhatsApp session from the session generator. Everything else has a default; this one does not, because the bot cannot connect without it.

OWNER_NUMBER and BOT_NAME

OWNER_NUMBER is your WhatsApp number with its country code, which the README table says the bot can otherwise detect automatically. BOT_NAME is the bot display name and ships as Silva MD.

PREFIX

The command prefix, shipped as a dot. The README prefix control section explains that the owner can change it from a command or by speaking to Silva, and can set it to null, none or off for prefix free commands, with the change written into config.env for the next restart.

MODE and THEME

MODE ships as public, with private, group and inbox as the other values the README table names. THEME ships as silva and selects the bot personality from the themes table.

Agent v2 Settings

AGENT_API_KEY ships empty, in which case the README says ch.at is used. AGENT_API_URL and AGENT_MODEL let an owner point the agent at a structured provider, and AGENT_MAX_STEPS ships at 5 with a cap of 8 in the README table.

Status and Protection Defaults

AUTO_STATUS_SEEN and AUTO_STATUS_REACT ship on and AUTO_STATUS_REPLY ships off. In the protection table, ANTICALL, ANTIDELETE_GROUP, ANTIDELETE_PRIVATE and ANTIVV ship on, and ANTILINK ships off, so link removal from non admins is the one protection a new owner must deliberately enable.

Behaviour and DATABASE_URL

ALWAYS_ONLINE, AUTO_TYPING and AUTO_BIO ship on; AUTO_REACT_MESSAGES and READ_MESSAGE ship off. DATABASE_URL is the optional switch for the encrypted PostgreSQL storage the README documents: leave it unset and the bot runs without it, and never commit a real connection string to a repository.

Official Links

SILVA MD Official Links

The resources checked for this guide: the repository and its README, the session selector and hosting addresses the README prints with their present day status stated honestly, the project website and channel, and the library the bot is built on.

SILVA MD GitHub Repository

The SilvaTechB/silva-md-bot repository, carrying the README, config.js, config.env.example, package.json and LICENSE file this guide verified against. It loads today and is actively maintained.

https://github.com/SilvaTechB/silva-md-bot

SILVA MD Session Selector

The silva-session-selector.vercel.app site named in the repository homepage. It loads today and presents the connection choice the README Step 1 section documents: QR Code or Pairing Code, then copy the SESSION_ID shown.

https://silva-session-selector.vercel.app/

Silva Host

The project own hosting platform at host.silvatech.co.ke, which the README recommends as its official and easiest deployment route. It loads today.

https://host.silvatech.co.ke/

SILVA MD Fork Checker (Offline)

The silva-md-fork-checker.vercel.app page the README Heroku method sends readers to for its Deploy to Heroku button. It returns a 404 error today, checked for this guide, so that documented route is broken; it is listed for the record, not as a working page.

https://silva-md-fork-checker.vercel.app/

TalkDrove Hosting Page (Did Not Load)

The host.talkdrove.com share page for this bot that the README TalkDrove method uses. It did not load when checked for this guide, the connection failing outright, and is listed with that status stated.

https://host.talkdrove.com/share-bot/49

Silva Tech Website

The silvatech.co.ke website of the Silva Tech Inc project, also named as the homepage in the repository package file. It loads today.

https://silvatech.co.ke

SILVA MD WhatsApp Channel

The WhatsApp channel the README links in its Connect With Silva section, presented there as the place to follow the project.

https://whatsapp.com/channel/0029VaAkETLLY6d8qhLmZt2v

Baileys Library

The current home of the Baileys library under the WhiskeySockets name. The package file of SILVA MD describes the bot as built with Node.js and Baileys.

https://github.com/WhiskeySockets/Baileys

Safety

Is SILVA MD WhatsApp Bot Safe?

The warning the README prints about the Session ID, the privacy weight of the anti delete and anti view once features, and the plain ban risk that applies to this bot like every other.

SILVA MD is an unofficial third party bot. Its README header advertises anti ban protection among its presentation lines; read that the way this guide reads every such claim: it is the project own marketing wording, and no feature in any bot can guarantee that a WhatsApp account will never be restricted. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect. Use a separate number for testing rather than your main personal or business number, and avoid spam and abusive automation of any kind.

The README itself states the sharpest risk plainly: your Session ID grants full access to your WhatsApp account, and it must never be shared. Keep it out of public repositories, screenshots and group chats, and keep a DATABASE_URL private for the same reason if you enable the encrypted storage. The project is open, so read its JavaScript files, plugins and configuration before running them, and be careful with the two features that touch other people privacy: anti delete and anti view once work by forwarding deleted messages and view once media to the bot owner, so consider the people in your chats before enabling them.

On routes, trust only what the repository itself links. The session selector in the repository homepage loads and matches the README flow. The fork checker page behind the README Heroku method returns a 404 error today, so if you follow that method, work from your own fork and the Heroku dashboard directly rather than through any replacement checker page a stranger offers you. On licensing, the LICENSE file carries the MIT License text with a Silva Tech Nexus copyright line and the GitHub API detects MIT for the repository.

Alternatives

Free MD Bots You Can Deploy on AHMED X

Want more free MD bots like this? These bots on AHMED X cover the same ground: free deploy, pair-code setup, group and chat automation.

ASTRA X

ASTRA X

WhatsApp MD Bot

Advanced AI-first MD bot with dual AI engines, media downloaders and deep group management.

Geston-MD

Geston-MD

WhatsApp MD Bot

Lightning-fast Baileys multi-device bot with AI chat, group protection and replies in many languages.

CELESTIA

CELESTIA

WhatsApp MD Bot

A polished multi-device WhatsApp bot with a large command library, AI chat and safe group tools.

TOXIC-MD

TOXIC-MD

WhatsApp MD Bot

Lightning-fast WhatsApp bot built on Baileys, made for speed and everyday automation.

SUKUNA-MD

SUKUNA-MD

WhatsApp MD Bot

A modular WhatsApp MD bot with group administration, media tools, protection engines and AI voice replies.

Levanter

Levanter

WhatsApp MD Bot

Multi-device WhatsApp bot packed with group protection, AI chat and a plugin system.

View all bots in the catalog

FAQ

SILVA MD FAQs

Short answers to the questions readers ask most about SILVA MD.

SILVA MD is a third party WhatsApp Multi Device bot developed under the Silva Tech Inc project and published at github.com/SilvaTechB/silva-md-bot. Its README documents an Agent v2 AI assistant, media downloaders, a protection suite, group management, games, utility tools and multiple themes, all controlled through environment settings.

Open the session selector named in the repository homepage, silva-session-selector.vercel.app, which loads today. The README Step 1 flow is: choose QR Code or Pairing Code, link your WhatsApp from Linked Devices, copy the SESSION_ID shown, and paste it into your host secrets panel. The README warns that the Session ID grants full access to your account and must never be shared.

Yes. The README explicitly documents both authentication methods, QR code and pairing code, in its Step 1 session section and again in the flow the session selector implements.

The README documents Silva Host as its recommended route, plus Heroku, Railway, Koyeb, Replit and TalkDrove, and a manual Node.js installation. Two routes have present day problems: the fork checker page the Heroku method depends on returns a 404 error today, and the TalkDrove sharing page did not load when checked for this guide.

A dot, per the README environment table. The owner can change it through the documented prefix controls, or switch to prefix free commands entirely, and can always talk to the assistant by starting a message with the word Silva.

Node.js 20 or newer. The README manual installation lists it as a requirement, the package file engines field specifies Node 20, and the documented start command is node silva.js.

The MIT License. The LICENSE file in the repository carries the MIT License text with a copyright line for Silva Tech Nexus, and the GitHub API detects MIT for the repository, so the records agree.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the SILVA MD repository as it could be opened on the last verified date: SilvaTechB/silva-md-bot, read through the GitHub API and its raw files, including its full README with its session steps, deploy tables, environment variable tables, feature tables and command tables, its package.json, its LICENSE file and its repository tree. The session selector named in the repository homepage was opened and loads, presenting its connection choice in the browser; the two methods the README documents for it are the ones this guide records. Silva Host and the Silva Tech website load. The fork checker page behind the README Heroku method returns a 404 error, and the TalkDrove sharing page did not load. Two README presentation habits are handled the same way throughout: its header advertises a command count and gives two different figures for it in two different places, so this guide publishes no command count at all, and its Agent v2 backend and encrypted storage descriptions are reported as the project documented design rather than as independently tested behaviour. Where the records publish nothing, this guide says so instead of filling the gap.

AHMED X provides this article for educational and informational purposes only. AHMED X is not the developer or owner of SILVA MD and does not claim any partnership or official affiliation with Silva Tech Inc or the project contributors.

AHMED X is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta. WhatsApp is a trademark of its respective owner. Use unofficial WhatsApp automation at your own risk.

Keep Reading

Related WhatsApp Bot Guides

More free WhatsApp bot guides from the AHMED X blog.

Guide

What Is SUBZERO MD WhatsApp Bot?

SUBZERO MD is a third party WhatsApp Multi Device bot project by Darrell Mucheri, known online as Mr Frank, built with JavaScript and presented by its README as version 7. Its GitHub repository is live and links a working session service that offers both pair code and QR code login. One caution runs through this guide: the README itself publishes no feature catalogue and no command list, so the feature descriptions in circulation come from the developer project websites, and this guide keeps those two records separate throughout.

Read the guide
Guide

SUHAIL MD WhatsApp Bot: Features, Session ID and Deployment Guide

SUHAIL MD is an older third party WhatsApp Multi Device bot project from the Suhail Tech Info name, built on the Baileys library and designed around entertainment and interactive games. The plain facts first: the original GitHub repository cannot be opened today, the GitHub API reports its access as blocked, and the project appears no longer maintained, with the developer channel having directed users to a newer project called Suhail X, whose repository is also blocked on GitHub today. Everything in this guide is therefore checked against a publicly accessible copy of the repository, reu12th/Suhail-Md-Railway, which preserves the README and the project files, and this guide covers the original SUHAIL MD only, not SUHAIL MD V2 and not Suhail X.

Read the guide
Guide

SULA MD WhatsApp Bot: Features, Pairing Code and Deployment Guide

SULA MD is a third party WhatsApp Multi Device bot project by Sulaksha Madara, and two different things share its name. The first is the GitHub project: the repository that survives today under the developer account holds the application files, sula.js, settings.js, package.json, app.json and an Apache License, but no README at all. The second is the newer SULA OFC web platform at sulaofc.store, which offers cloud bot deployment through pair code connection and advertises its own feature set. The README that documented pairing and deployment buttons for the GitHub project lived on a second repository address, SULA-MD-NEW/SULA-MD, which returns a 404 error today. This guide keeps the repository and the platform separate from the first line to the last, exactly because mixing them produces wrong instructions.

Read the guide
Guide

SUPUN MD WhatsApp Bot: Features, Session ID and Deployment Guide

SUPUN MD is a third party WhatsApp Multi Device bot project by Mr. Supun Fernando, a developer from Sri Lanka who also works under the name Dark Shadow Modz. The first fact a reader needs is where the project can still be read: the original repository, mrsupunfernando12/SUPUN-MD, returns a 404 error today, and the developer GitHub account behind it returns a 404 error as well. The record survives in partial copies, one on GitLab under the Nadu-12 account and one on GitHub under the iam-dsmodz account, and in three developer pages that still load. The pages load, but every pairing service behind them returns a 404 error today, so this guide links no working session service for SUPUN MD. A security report covered in the safety section gives readers a second reason to check every dependency carefully before running anything connected to this project name.

Read the guide

Deploy Your Own Free WhatsApp Bot Today

Pick a bot from the AHMED X catalog and deploy it free in minutes. No server, no coding.

Browse Free Bots