Back to PLOGME home
⚉

CODY AI 🜲v2

WhatsApp Bot — Deploy Suite

Link your WhatsApp
This controls the session ID sent to WhatsApp and filled into Generate Script.
Your pair code will appear here
QR Code

Scan this QR code with WhatsApp

Configure your deployment
Controls bot-local times and daily schedules. Example: America/Toronto.
Auto Read Messages Bot marks messages as read automatically
Auto View Statuses Bot automatically views WhatsApp statuses
Always OnlineKeep the bot presence online
Anti-CallReject incoming WhatsApp calls
Auto Like StatusLike viewed statuses
PLOGME auto-repliesEnable global private-chat PLOGME mode on first deploy
Auto-updateUpdate CODY before startup; existing setting is preserved
index.js
Fill in your details above, then click
Generate index.js
node index.js Save the file and run this — that's it.
Deployment instructions
  1. 1
    Create a Render account
    Go to render.com and sign up — linking with GitHub makes the next step easier.
  2. 2
    New Background Worker
    Click New + → Background Worker. Connect your GitHub repo or paste this URL directly:
    https://github.com/crysnovax/CODY
  3. 3
    Set build & start commands
    In the service settings, configure these two commands:
    npm install
    node index.js
  4. 4
    Add Environment Variables
    Under the Environment tab, add these key-value pairs:
    SESSION_ID
    OWNER_NUMBER
    OWNER_NAME
    BOT_NAME
    PREFIX
    MODE
    💡 Or skip env vars entirely — use the Generate Script tab to embed values directly.
  5. 5
    Deploy ✅
    Click Create Background Worker. Render will build and launch your bot automatically.
Free tier Render services spin down after inactivity. For a 24/7 bot, upgrade to a paid plan ($7/mo) or deploy on a VPS instead.
  1. 1
    Install Node.js 20, Git & PM2
    SSH into your server and run this single block:
    curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - && sudo apt-get install -y nodejs git && sudo npm install -g pm2
  2. 2
    Create folder & upload index.js
    Create a folder for your bot:
    mkdir cody-ai && cd cody-ai
    Then upload your generated index.js using any of these methods:
    • SFTP — use FileZilla or Termius file transfer
    • cat command — paste content directly into terminal:
    cat > index.js << 'EOF' [paste your index.js content here] EOF
  3. 3
    Create package.json
    Run this to create a minimal package.json:
    echo '{"name":"cody-ai","version":"1.0.0","type":"commonjs","scripts":{"start":"node index.js"}}' > package.json
  4. 4
    Launch with PM2
    Start the bot and keep it alive 24/7:
    pm2 start index.js --name cody-ai
    pm2 save && pm2 startup
  5. 5
    Useful PM2 commands
    pm2 logs cody-ai
    pm2 restart cody-ai
    pm2 stop cody-ai
    pm2 delete cody-ai
Recommended providers: Oracle Cloud (always free), DigitalOcean, Hetzner, or Contabo. Ubuntu 22.04 LTS works best. Minimum 512MB RAM required.
  1. 1
    Create a Node.js server
    In your panel (Pterodactyl, Pelican, etc.), create a new server using a Node.js egg / template. Set RAM to at least 512 MB.
  2. 2
    Upload index.js
    Use the panel's file manager to upload your generated index.js to the server root.
  3. 3
    Set the startup command
    In Startup settings, change the start command to:
    node index.js
  4. 4
    Power on ✅
    Click the power button and watch the console. Your bot will install dependencies and go online automatically.
No Node.js egg available? Ask your host to install one from github.com/parkervcp/eggs.
  1. 1
    Update Termux
    Open Termux and update all packages:
    pkg update -y && pkg upgrade -y
  2. 2
    Install Node.js & Git
    pkg install nodejs-lts git -y
  3. 3
    Clone CODY AI
    git clone https://github.com/crysnovax/CODY.git
    cd CODY
  4. 4
    Install Dependencies
    npm install
  5. 5
    24/7 Session (Recommended)
    pkg install tmux -y
    tmux new -s cody
  6. 6
    Start CODY AI
    node index.js
Termux does not support sudo commands. Use pkg instead of apt-get. Running inside tmux helps keep the bot alive when the Termux window is closed.