AHMEDX
Guide

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

VAJIRA MD is a third party WhatsApp Multi Device bot project by Vajira Rathnayaka, a developer from Sri Lanka who also works under the name Vajira T.D.D. The first fact a reader needs is the state of the record: every repository under the developer own accounts returns an access blocked notice from GitHub today, and the repository copy that carried the V9 README has been deleted outright. What survives is an older V7 README preserved in a public copy, a partial set of the project deployment files preserved in another, and a live Railway template that still names the developer and still requires a Session ID, while pointing at a repository nobody can open. This guide is checked against those surviving records, presents the V9 material only where a surviving file corroborates it, and says plainly where the documentation can no longer be rechecked at all.

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

About

What Is VAJIRA MD WhatsApp Bot?

What the project is, who developed it, and the present day state of its repositories, in which every developer account repo is access blocked and the V9 documentation copy is gone.

VAJIRA MD is a third party WhatsApp Multi Device bot project associated with Vajira Rathnayaka, also known as Vajira T.D.D. The V7 README preserved in a public copy carries an author badge in his name and a developer team table headed by Vajira T.D.D as Founder and Developer, with team roles covering coding, testing, design, tool supply and management under the team name Technical Cybers. The live Railway deployment template for the project independently names Vajira Rathnayaka as the developer. The project went through several versions: a V7 README and a V9 README both circulated, the versions are not interchangeable, and the package file in the surviving files copy carries yet another version string, 11.3.0. This guide reports each version label exactly where it appears rather than merging them.

The repository situation is the worst in this series, and it has to be stated before anything else. The developer own repositories, VajiraTechOfficial/VAJIRA_MD, VajiraTech/VAJIRA_MD, vajiratech/vajira-md and vajiratech/vajira-md-new, all return the same response from the GitHub API today: repository access blocked. They cannot be read, forked or checked. The copy that carried the V9 README, mxn-movie/vajira-md, returns a 404 error, and no archived snapshot of it could be found. A project in this state cannot be installed from its own documentation, and any guide that presents its routes as working is describing a record that no longer exists.

What survives is two partial records. A public copy under the demithdj account carries the full V7 README: its fork step, its Get Session step with two session services, its deployment methods link, a Heroku deployment video, the developer team table and a sample Node.js workflow. A second copy under the VajiraOfficialBot account carries no README at all, but holds the project deployment files: app.json, package.json, settings.js, a talkdrove.json and a LICENSE file, beside a session folder. Between those two copies and the live Railway template, the shape of the project can still be verified, and that is what this guide does. Material that only the lost V9 README contained, including a support bot reference and a long Koyeb configuration list, could not be rechecked against any readable record and is not republished here as fact.

Features

VAJIRA MD WhatsApp Bot Features

No surviving record publishes a feature catalogue for VAJIRA MD, so the cards below cover only what the V7 README and the surviving deployment files actually document: the connection model, the session method, the operating modes and the project structure.

WhatsApp Multi Device Support

VAJIRA MD is presented across its records as a WhatsApp Multi Device bot that operates through a linked WhatsApp account. The V7 README header, the Railway template description and the deployment files all describe the same kind of application.

QR Code Session Authentication

The project own deployment file describes its required Session ID as the one you got from scanning QR, and the session buttons in the V7 README are labelled QR OR PAIR CODE. Session generation for this project is a scanning flow, whatever the version, and no separate pairing code service for it could be verified in any surviving record.

Button and Nonbutton Operating Modes

The surviving app.json requires a MODE setting whose shipped value is nonbutton, and its own description explains the choice: nonbutton for number reply operation, button for button reply operation. The settings file in the same copy defaults MODE to nonbutton as well. The V9 README presented the same choice as two commands, .mode button and .mode nonbutton, and those are the only two commands this guide publishes for VAJIRA MD, because they are the only ones its records name.

Session Folder Application Structure

The package file in the surviving copy names session/start.js as the application entry point, runs a decode step before install completes, and starts the application from that session folder. The copy also carries a session folder beside it. That is the startup shape the project files define, recorded here because it differs from the single file entry point most bots in this series use.

Deployment Files for Heroku and TalkDrove

The surviving copy is essentially a set of deployment files: app.json shaped for Heroku, with a Node.js buildpack and the heroku-24 stack, and a talkdrove.json shaped for the TalkDrove bot hosting service, each requiring a Session ID. A Railway template also exists and still loads. The deployment section gives each route its present day status.

A Documented Developer Team

The V7 README publishes a developer team table: Vajira T.D.D as Founder and Developer, with named roles for a co-coder, bug and tool suppliers, group management, bug testers, a logo designer and a movie controller, under the team name Technical Cybers. Few projects in this series document their team at all, so the record is worth keeping.

No Published Feature or Command Catalogue

This card states a negative plainly. No surviving record publishes a media, AI, entertainment or group administration feature list for VAJIRA MD, and no command reference beyond the two mode commands could be verified. This guide invents none, and any detailed VAJIRA MD feature list found elsewhere does not come from documentation this guide could check.

Session ID

How to Get a VAJIRA MD Session ID

The documented session flow in the surviving V7 README runs through two session services, one on Heroku and one on Koyeb, both labelled QR OR PAIR CODE. Both were opened again for this guide and both return a 404 error. The V9 documentation is lost, and no verified session generator for any version could be established, so this section records the documented route and its present day condition plainly.

01

Start From the Project Documentation, Knowing Its State

The surviving V7 README puts Get Session at step two of its setup, after forking the repository. Both of those steps belong to repositories and services that can no longer be opened, so treat this section as the documented shape of the process, not as a route that works today.

02

Fork Step: Documented, Not Currently Possible

The READMEs instruct users to fork the project before deployment. The developer repositories that the fork buttons point at return access blocked notices from GitHub today, so the fork step cannot be completed as written, and copies under other accounts are not the developer own source.

03

The Two V7 Session Services

The V7 README Get Session step offers two services behind buttons labelled QR OR PAIR CODE: a session application on Heroku and a session application on Koyeb. The README adds its own note that if the session does not come, a VPN should be used and the request tried again. Those buttons are the only session services any surviving VAJIRA MD record publishes.

04

Both Session Services Return 404 Today

Both addresses were opened again for this guide, and both return a 404 error. Combined with the lost V9 documentation, that means no working official session service for VAJIRA MD could be confirmed for any version, and this guide links neither address as a working service.

05

QR Scanning Is the Documented Method

Where the records describe the method at all, they describe scanning. The app.json in the surviving copy describes its required SESSION_ID as the session you got from scanning QR, and the general flow behind such a service is the standard one: open WhatsApp, go to Linked Devices, choose Link a Device, and scan the code the service displays. A dedicated pairing code service for VAJIRA MD is not documented in any record this guide could read.

06

Where the Session ID Goes

Every surviving deployment file consumes the same value: SESSION_ID is a required setting in app.json, in talkdrove.json and in the live Railway template. Keep that value private, because anyone holding working session credentials may be able to access the WhatsApp session they came from.

07

Avoid Unrelated Session Generators

With the developer repositories blocked, the V9 documentation deleted and both documented session services returning 404, any unrelated website using the VAJIRA MD name to offer session generation is not backed by project documentation this guide could check. Never type your number into such a page and never pay for a session for this bot.

Deployment

How to Deploy VAJIRA MD WhatsApp Bot

The deployment record for VAJIRA MD is a set of routes in different states: a Railway template that loads but deploys a blocked repository, Heroku and TalkDrove shapes preserved in the surviving files, a Koyeb route that only the lost V9 README documented, and a manual Node.js flow preserved in the V7 README workflow. Each is presented with its present day status.

01

Read the Repository Status First

Every route in this section depends on source code, and the source repositories are the problem: the developer own repositories are access blocked on GitHub and the V9 copy is deleted. Expect each route below to fail at the source step, and treat any service still offering one click VAJIRA MD deployment with suspicion.

02

Railway: The Template Loads, Its Repository Is Blocked

The Railway template page for VAJIRA MD opens today. It presents the project as a WhatsApp bot developed by Vajira Rathnayaka, lists SESSION_ID among its variables as a required value, and deploys the repository github.com/VajiraTechOfficial/VAJIRA_MD. That repository is one of the access blocked ones, so the template survives while the code it installs cannot be fetched. This guide records the template as live and its route as unusable in the same sentence, because both halves are true.

03

Heroku Shape: app.json

The surviving copy carries an app.json naming the app VAJIRA-MD-X. It requires SESSION_ID and MODE, the mode value shipping as nonbutton, and declares the Heroku Node.js buildpack on the heroku-24 stack. The V7 README also links a Heroku deployment video. That is the shape of a Heroku route prepared in files and presented in a video, checked against a copy, for a repository that cannot currently be forked.

04

TalkDrove: The File Survives, the Page Does Not Respond

The surviving copy carries a talkdrove.json for the TalkDrove bot hosting service, requiring SESSION_ID and offering MODE, which proves the route was prepared for this project. The TalkDrove share page the V9 README linked was checked for this guide and its host did not respond at all, so the route cannot be presented as available.

05

Koyeb: Documented Only in the Lost V9 README

The V9 README documented a Koyeb deployment route with a long list of environment variables. That README has been deleted with its repository, no surviving file carries the list, and the one Koyeb address a surviving record does hold, the V7 session service, returns a 404 error. This guide therefore publishes no Koyeb procedure and no variable list for VAJIRA MD, rather than repeat documentation nobody can recheck.

06

Manual Flow From the V7 README Workflow

The V7 README publishes a sample Node.js workflow, and it is the only complete manual flow a surviving record gives: Node.js 20, install dependencies with npm install, and start with npm start. The package file in the surviving copy gives that start command a precise meaning: it runs node session/start.js, after a preinstall step that runs the session decode file. Work only from a copy you have reviewed in full, and replace the shipped default values in its settings file, which include database credentials that belong to the project side, with your own.

Configuration

VAJIRA MD Configuration Settings

The configuration evidence that survives is short and consistent: two required settings appear in every deployment file the copies hold. This section records those two, the files that carry them, and the one longer list that could not be rechecked and is therefore not published.

SESSION_ID

The one credential every route requires. app.json describes it as the Session ID you got from scanning QR, talkdrove.json requires it with an empty shipped value, and the live Railway template lists it as a required variable. Every deployment shape this project prepared depends on this single value being present and private.

MODE

The operating mode setting, required in app.json with the shipped value nonbutton and described there in the project own words as the choice between number reply operation in nonbutton mode and button reply operation in button mode. The settings file in the same copy defaults MODE to nonbutton, and the V9 README presented the same switch as the .mode button and .mode nonbutton commands.

The Files That Carry the Settings

Configuration evidence for VAJIRA MD lives in deployment files rather than a settings manual: app.json and talkdrove.json in the VajiraOfficialBot copy, the settings.js file beside them, and the variable list of the Railway template. The settings file ships with default values of its own, including a database connection value with project side credentials written into it. Replace every shipped default with your own and never publish the file with the project defaults still inside.

The Koyeb Variable List That Could Not Be Rechecked

The lost V9 README reportedly carried a longer configuration list for its Koyeb route, running to more than a dozen variable names. No surviving file contains that list, and this guide does not republish it. Readers who meet the list elsewhere should know it comes from documentation that can no longer be opened, quoted from a README that has been deleted.

Official Links

VAJIRA MD Official Links

The resources checked for this guide: the two surviving copies, the live Railway template, the developer repositories GitHub has blocked, the deleted V9 copy, the project channel its V7 README links, and the session services that no longer load, each with its check result stated honestly.

VAJIRA MD V7 README (Surviving Copy)

The copy at github.com/demithdj/Vajira-md, which carries the full V7 README: the fork step, the Get Session step, the deployment methods link, the developer team table and the sample Node.js workflow this guide verified against. A copy under another account, listed as a copy.

https://github.com/demithdj/Vajira-md

VAJIRA MD Deployment Files (Surviving Copy)

The copy at github.com/VajiraOfficialBot/VAJIRA-MD, holding app.json, package.json, settings.js, talkdrove.json, a session folder and the LICENSE file, with no README. The deployment file facts in this guide come from this copy.

https://github.com/VajiraOfficialBot/VAJIRA-MD

Railway Deployment Template

The Railway template page for VAJIRA MD, which loads today, names Vajira Rathnayaka as the developer and lists SESSION_ID as a required variable. It deploys the VajiraTechOfficial/VAJIRA_MD repository, which GitHub has access blocked, so the route cannot currently be completed.

https://railway.com/deploy/vajira-md--_vD3X2

Developer Repository VajiraTechOfficial/VAJIRA_MD (Access Blocked)

The repository the Railway template points to. The GitHub API reports it as repository access blocked today. Listed for the record, not as a working source.

https://github.com/VajiraTechOfficial/VAJIRA_MD

Developer Repository VajiraTech/VAJIRA_MD (Access Blocked)

The repository the V7 README badges, fork button and workflow point to. It likewise returns an access blocked response from the GitHub API today. Listed for the record, not as a working source.

https://github.com/VajiraTech/VAJIRA_MD

VAJIRA MD V9 README Copy (Offline)

The mxn-movie/vajira-md address that carried the V9 README this project documentation was drawn from. It returns a 404 error today and no archived snapshot of it could be found. Listed for the record, not as a working source.

https://github.com/mxn-movie/vajira-md

VAJIRA MD WhatsApp Channel

The WhatsApp channel the V7 README links under its Follow Our Channel heading, presented there as the place to follow the project.

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

Session Service on Heroku (Offline)

The first session service behind the V7 README Get Session buttons. It returns a 404 error today, checked for this guide, and is listed for the record, not as a working service.

https://vajirasession-430ab1324465.herokuapp.com/

Session Service on Koyeb (Offline)

The second session service behind the V7 README Get Session buttons. It returns a 404 error today, checked for this guide, and is listed for the record, not as a working service.

https://stuck-godiva-vajiratech2003-a4248d0c.koyeb.app/

TalkDrove Deployment Page (Not Responding)

The TalkDrove share page the project documentation linked for hosted deployment. Its host did not respond at all when checked for this guide. Listed for the record, not as a working service.

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

Safety

Is VAJIRA MD WhatsApp Bot Safe?

The precautions that apply to VAJIRA MD, including the risks created by its blocked repositories and deleted documentation, and the shipped default credentials sitting inside its surviving settings file.

VAJIRA MD is an unofficial third party bot. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no feature in any bot can promise protection from that. Use a separate number for testing rather than your main personal or business number, and avoid spam and abusive automation of any kind.

Understand the present day state before connecting anything. The developer repositories are access blocked, the V9 documentation is deleted, both documented session services return 404 errors, and the one live template deploys a repository nobody can open. A vacuum of this kind is exactly what fake session websites and repackaged downloads exploit. Copies of this project circulate widely under its name, including renamed and reworked variants, and a copy under another account is not the developer own source. Only trust authentication and download links you can trace back to the records themselves, and treat every other VAJIRA MD page as unverified.

Check the shipped files before you run anything. The settings file in the surviving copy ships with default values written into the code, including a database connection value carrying project side credentials. Those values belong to the project side: never rely on them, never treat them as yours, and replace them with your own database and your own settings before any run. Never share your own Session ID in chats, screenshots or public forks, and if you publish a copy of the project, publish it with your own credentials removed, not carried along inside it.

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

VAJIRA MD FAQs

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

VAJIRA MD is a third party WhatsApp Multi Device bot project associated with Vajira Rathnayaka, also known as Vajira T.D.D. Its surviving records document QR code session generation, a required Session ID, button and nonbutton operating modes, and deployment files for Heroku, TalkDrove and Railway. It circulated in several versions, including V7 and V9 presentations.

The project is associated with Vajira Rathnayaka. The V7 README carries an author badge in his name and a developer team table headed by Vajira T.D.D as Founder and Developer under the team name Technical Cybers, and the live Railway template independently describes the bot as developed by Vajira Rathnayaka.

Not the developer own ones. VajiraTechOfficial/VAJIRA_MD, VajiraTech/VAJIRA_MD, vajiratech/vajira-md and vajiratech/vajira-md-new all return a repository access blocked response from the GitHub API today, and the mxn-movie copy that carried the V9 README returns a 404 error. What survives is a V7 README copy under the demithdj account and a deployment files copy under the VajiraOfficialBot account.

The documented method is QR scanning: the app.json in the surviving copy describes the required SESSION_ID as the session you got from scanning QR, and the V7 README Get Session step links two services behind buttons labelled QR OR PAIR CODE. Both of those services were opened again for this guide and both return a 404 error today, so no working official session service for VAJIRA MD could be confirmed.

No dedicated pairing code service could be verified. The V7 README session buttons carry a QR OR PAIR CODE label, but they point at the same two session services, both now returning 404, and the deployment files describe the session purely as the product of scanning QR. This guide links no pairing service for VAJIRA MD as a working service.

Only two commands are named anywhere in the records this guide could check: .mode button and .mode nonbutton, which switch the bot between button reply and number reply operation. The mode system behind them is corroborated by the surviving app.json and settings file, where MODE defaults to nonbutton. No other command names, categories or prefix could be verified, so this guide publishes no command list.

The records name Heroku, TalkDrove, Koyeb and Railway, and none of the routes is usable as documented today. The Railway template still loads and requires SESSION_ID, but it deploys a repository GitHub has access blocked. The Heroku and TalkDrove shapes survive as files in a copy, while the TalkDrove host does not respond. The Koyeb route was documented only in the deleted V9 README. The manual flow in the V7 README workflow is Node.js 20, npm install and npm start.

The records do not agree on a single version, and this guide does not merge them. A V7 README survives in full, a V9 README circulated until its repository was deleted, the app.json in the surviving copy names the app VAJIRA-MD-X, and the package file in the same copy carries version 11.3.0. Treat any single version claim for this project with care and check it against the exact copy in front of you.

The LICENSE file in the readable VajiraOfficialBot copy carries the full text of the Apache License 2.0. The developer own repositories are access blocked, so their LICENSE files cannot be checked, and this guide reports the license exactly at that level: Apache License 2.0 is the license the surviving copy of the project files carries.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the VAJIRA MD records that could be opened on the last verified date: the V7 README preserved in the public copy at demithdj/Vajira-md, read in full; the deployment files preserved in the copy at VajiraOfficialBot/VAJIRA-MD, including its app.json, package.json, settings.js, talkdrove.json and LICENSE file; and the live Railway template page. On that date every developer repository returned an access blocked response from the GitHub API, the mxn-movie copy that carried the V9 README returned a 404 error with no archived snapshot available, both V7 session services and the V7 deployment methods page returned 404 errors, and the TalkDrove host did not respond. Material that only the lost V9 README contained, including its Koyeb configuration list and its support bot reference, could not be rechecked and is not republished as fact. The developer contact number on the Railway template and the database credentials shipped inside the surviving settings file are not reproduced in this guide. 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 VAJIRA MD and does not claim any partnership or official affiliation with Vajira Rathnayaka 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

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

VENOM MD is a third party WhatsApp Multi Device bot project published by Bryan Tech, and unlike many projects in this series its original GitHub repository, Bryanlover1/VENOM-MD, still opens today, so this guide is checked against the repository itself: its README read in raw form, its full file tree, its package file, its example environment file, its settings file, its Heroku configuration and its LICENSE file. Two findings shape everything about using this bot. The README itself states, in its own capital letters, that its pairing code route temporarily uses the Naruto MD pairing service, and both authentication services it links return a 404 error today. And the repository package file does not match the project it sits in: it names the package MADARA-MD and points at a main file the repository root does not contain. Both facts are recorded plainly in the sections below.

Read the guide
Guide

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

WASI MD is a third party WhatsApp Multi Device bot project by Itxxwasi, also presented as Mr Wasi, and the identifiable current project is WASI MD V7 in his own GitHub repository. The original repository is live and was read in full for this guide: its README documents the feature categories and command tables, its .env.example and config.js carry the settings, and its troubleshooting section describes QR authentication with a delete the session folder and rescan flow. The project publishes no pairing website for V7, and the developer separate session generator repository today links to a website that shows unrelated proxy content, so this guide links no WASI MD pairing page as a working service.

Read the guide
Guide

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

XBOT MD, written X BOT MD inside its repository, is a third party WhatsApp Multi Device bot project by Aswin Sparky. The original repository is live today under the renamed Aswin-Sparky account, with the older A-S-W-I-N-S-P-A-R-K-Y address redirecting to it, and this guide is checked against that repository directly: its README documents QR authentication and four deployment routes, and its session service was opened again for this guide and is working, asking visitors to sign in with GitHub and fork the repository before it offers QR pairing and a pair code option. A separate pairing project by the same developer exists only as source code to host yourself, and the README publishes no command list, so this guide publishes none.

Read the guide
Guide

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

ZOKOU MD, also known as Zokou 2.0, is a third party WhatsApp Multi Device bot project by Djalega++ and Monkey D Luffy, documented in a French language README in its original GitHub repository. That repository is live today and was read in the original French for this guide: it documents the feature list, links one session website, and gives Heroku and Koyeb deployment routes. The session website was opened again for this guide and its QR route loads, while the pairing code destination it links out to returns a 404 error, and the README Heroku button in fact templates a different repository, so this guide states the present day condition of every route plainly.

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