Ririko AI 2.0.0

Ririko is a multipurpose Discord bot you host yourself. It plays music, chats with AI, moderates your server, runs an economy with levels, hosts giveaways and mini-games, and has a card game of its own, the Waifu TCG. A web dashboard lets server admins change every setting without a command.

Version 2.0.0 is a full rewrite of RirikoBot 1.4.0 in TypeScript. It keeps every 1.x command, with a slash and a prefix version of each.

What you get	In short
Music	Play from YouTube, Spotify, SoundCloud, Deezer and more through Lavalink 4, with a live player message.
AI chat and images	Gemini, OpenAI-compatible APIs and Ollama, with tools that respect Discord permissions.
Waifu TCG	Card drops, trading, gear, dungeons and seasonal bosses.
Moderation	Warnings, cases, AutoMod and raid alerts.
Economy and levels	Credits, XP, a daily reward, a bank and a shop.
Web dashboard	Sign in with Discord and manage each server from a browser.

Self-hosting means you run the bot, the dashboard, a PostgreSQL database and a Lavalink audio server on your own machine. Docker starts all four from one command, but the bot is online only while that machine is.

Quick start with Docker

The quickest start is the starter on npm. You need Node.js 20 or newer:

npx ririko --docker

It downloads the release files, runs the setup wizard and asks if it should start Ririko. Leave out --docker and it asks you to choose between Docker and a source install. The steps below do the same by hand.

You need Docker 23 or newer with Compose 2.24.4 or newer, Git, and a Discord account. The steps below are the short form of Deploy Ririko With Docker, which explains each one.

1. Clone the repository and check out the release:

   git clone https://github.com/RirikoAI/RirikoBot.git
   cd RirikoBot
   git checkout v2.0.0
   

2. Run the setup wizard. It opens in your browser at the address it prints, guides you through the Discord application, checks your values and writes .env.production:

   docker run --rm -it -p 127.0.0.1:3999:3999 -v "$PWD:/setup" ririkoai/ririkobot:2 ririko setup --docker --env-file /setup/.env.production --listen 0.0.0.0 --no-open
   

3. Start the stack:

   docker compose -f docker-compose.production.yml --env-file .env.production up -d
   

4. Add the bot to your server with the invite link on the wizard's Install page. Without the wizard link, use the Developer Portal steps in section 2.6 of the guide.

5. Register the slash commands:

   docker compose -f docker-compose.production.yml --env-file .env.production exec bot ririko commands:sync --global --all-guilds
   

   Then type /ping in your server. The bot answers.

Global commands can take a while to show in Discord. Press Ctrl+R in Discord to refresh.

Find your way

Run it

• Deploy Ririko With Docker: the full guide behind the quick start, including a public address and a remote Lavalink node.
• After You Install and Integrations: the optional settings and the key each feature needs.
• Upgrade From Ririko 1.4.0 to 2.0 and Move Your Data: for an existing 1.4.0 bot.

Use it

• Commands and Server Modules: every command and what each module does.
• Music, AI Chat and Images, Moderation and Economy and Levels.
• Web Dashboard: sign-in, every page and the owner console.
• Waifu TCG Player Guide and Adventures.

Build it

• CONTRIBUTING.md: how to make a change and open a pull request.
• SETUP.md: run Ririko from source on your own machine.
• Architecture, Developer Guide, Database Guide and Testing Guide.

Ask

• Join the Discord support server to ask for help or just chat.
• Open an issue for a bug or an idea.

Built with

Node.js 22, TypeScript (strict), pnpm workspaces, Discord.js 14, Drizzle ORM (PostgreSQL and SQLite), Lavalink 4, Next.js 16 and Vitest.

apps/       bot, web dashboard and the ririko command-line tool
packages/   core, database, discord, services, music and ai
assets/     TCG catalogs, installer guides and the images of this page
docs/       the documentation, also published at ririko.ai/docs

Security

Never commit .env, tokens, cookies or database files. Report vulnerabilities privately to the maintainers, not in public issues.

Contributors ✨

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!

License

MIT