Risutanium (a fork of RisuAI)

Risutanium (also written RisuTanium, Risu-Tan or RT) is a fork of RisuAI (called "upstream" below), a cross platform AI chatting application (desktop, web and self-hosted). The fork is for stabilization and improvement: fixing data-loss and reliability problems, and making targeted improvements. Characters, modules, presets, .bin backups and plugins made for upstream RisuAI must keep working here.

Status: there are no releases yet. This fork is experimental and heavily work in progress. There is nothing to download. You can build it from source or with Docker, as described below. Keep a .bin backup of anything you care about.

Features

• Many AI providers: OpenAI, Anthropic (Claude), Google (Gemini) and Vertex AI, Mistral, Cohere, NovelAI, NovelList, DeepSeek, DeepInfra, NanoGPT, AWS (Bedrock), AI Horde, Ollama, WebLLM (in-browser inference), OpenRouter and Ooba (Text Generation WebUI). Plugins can add more.
• Emotion Images: Show the character image that matches the current expression.
• Additional Assets: Embed images, audio and video in a character and show them in the chat or as the background.
• Group Chats: Multiple characters in one chat.
• Plugins: Add features and providers, and share them.
• Scripting: Regex scripts, trigger scripts, Lua scripting and modules.
• Translators: Translate input and output automatically.
• Lorebook: Also known as world info or memory book. It gives a character more to remember.
• UI modes: Standard Risu, Waifulike, Mobile Chat, CardBoard and Custom HTML, plus colour schemes.
• Prompting: Change the prompt order, and use conditions and variables.
• TTS: Read the output text aloud.
• Long-term memory: HypaMemory V2 and V3, SupaMemory and Hanurai Memory.

What's different from upstream

This is a short list of changes you will notice. See Migrating from upstream for moving your data.

• A new identity. The product is called Risutanium. The desktop app's identifier is io.github.yor42.risutanium, a fresh app-data folder on purpose. The version is SemVer from 0.1.0, with the upstream version it is based on as a suffix: the home screen's Version line shows 0.1.0-up2026.8.250. The desktop app registers two deep-link schemes, risutaniumlocal and risuailocal; the second stays so that upstream Realm's open-in-app links still reach the app. The in-app updater is switched off until the first release.
• The CBS version tags report this fork's version. {{version}} returns 0.1.0 and {{majorversion}} returns 0, so an upstream card that compares them against a 2026 version behaves differently.
• No RisuAccount and no Google Drive backup. Account sign-in, sync and Drive backup are removed. RisuRealm still works, and the first time you use it the app asks you to accept upstream's Terms of Service and Privacy Policy. Move data with a local .bin backup. A .bin made while signed in to RisuAccount on risuai.xyz cannot be read here.
• Saving across tabs and devices. A self-hosted Node server refuses a save from a stale tab instead of overwriting newer data. When another tab saves, a tab with no unsaved edits usually reloads, but not while it has an unsaved draft open, and not more than twice a minute. A tab with unsaved edits asks you first, and asks again at most once a minute. Between two devices there is no such prompt. If another device or browser saves to the same Node server first, the first device shows a message on its next save and stops saving until you reload that tab, and edits made there since its last successful save are lost when you reload. Opening the app on the other device can be enough, because archiving at startup can save even when you edit nothing. This is traced in the code and has not been run against a real server.
• Restoring a backup is guarded. Load Backup Locally and Load Internal Backup refuse to run on the web build while another tab of the app is open, and warn you if the browser cannot check. They also refuse while a reply is being written into a chat. Load Internal Backup now writes the snapshot as the main save and reloads the app.
• Local backups include every asset, not only .png files. Audio, video, WebP, JPEG, font and CSS assets are included. Inlay images, video and audio in chat messages are still not backed up.
• "Clean Unused Archived Data and Assets" is a guarded, manual clean-up. It refuses while a reply is being written, while saving has stopped, and while two characters share an id. It also refuses when the saved data has changed since the page last read it (or the page has no record of it yet), and on the web build while another tab is open. It also deletes unused asset files.
• Characters are archived at startup and load when you open them. The automatic 10-day archiving of characters is gone. Instead, on the desktop app and in browsers that support it, a pass at startup moves each eligible character's full data into a separate copy and leaves a small stub in the main save; the character loads when you open it, and nothing is deleted. It is on by default, and the app tells you the first time it archives. Turn it off in Settings > Advanced Settings > "Archive characters at startup".
• Work stays in the chat it started in. A reply, and the memory summaries and variable writes that come with it, are written into the chat the message was sent from, even if you switch chats, add a branch or reorder chats while it generates.
• Deleting a chat or character stops the work in it. Deleting a chat warns you if something is still writing into it, and deletes the chat you confirmed even if the list changed meanwhile.
• Escape no longer answers a prompt. Escape does nothing on a confirm or input prompt that waits for an answer, instead of answering it with an empty answer. It still closes information alerts.

Documentation

• Wiki: the pages in this repository, rewritten for this fork.
• Plugin development guide

Building from source

Prerequisites:

• Node.js 20.19+ or 22.12+.
• pnpm 10.34.1. package.json pins it, so corepack enable is enough.
• For the desktop build only: Rust and Cargo, plus the platform prerequisites in the Tauri guide.

pnpm install
pnpm dev          # web development server, http://localhost:5174
pnpm build        # web build into dist/
pnpm tauri dev    # desktop development
pnpm tauri build  # desktop build
pnpm check        # type checking
pnpm test         # unit tests

To run the self-hosted Node server, build the web app, then start the server from the repo root:

pnpm build
pnpm runserver

It serves dist/ and keeps its data in save/, both relative to the folder you start it from. It listens on port 6001, or on PORT if you set that.

The legal-documents notice

The frontend shows a "legal documents not configured" notice instead of the app when VITE_RISU_LEGAL_CONFIGURED is empty or unset at build time. In this repository it is on by default, because this fork has its own Terms of Service and Privacy Policy, linked from Settings. .env.production (read by pnpm build, pnpm buildsite, pnpm tauribuild and pnpm hono:build) and .env.development (read by pnpm dev) set it to TRUE, and the Docker build sets it too (see Docker). The unit tests do not load these files.

To opt out and get the notice, set the variable to an empty value in the environment of the build command. Vite lets an existing environment variable, even an empty one, override the .env.* files. In bash:

VITE_RISU_LEGAL_CONFIGURED= pnpm build

Windows cmd cannot hold an empty variable. There, and in any shell, you can instead put the line VITE_RISU_LEGAL_CONFIGURED= in an untracked .env.production.local (or .env.development.local for pnpm dev). It loads after the committed file and wins, and *.local is in .gitignore.

Known problems with the Node server

• A plain-HTTP address other than localhost does not work at present. Opening the server over a LAN or VPN address without HTTPS stops the boot with "Cannot read properties of undefined (reading 'generateKey')", because the browser does not offer crypto.subtle outside a secure context. localhost works. HTTPS has not been tested. This is tracked as CHORE-49 in Agents/Roadmap.md.
• The first run of a brand-new server can fail until you reload. The app asks you to set a password. After you enter it, the boot can stop with the alert "getItem Error". Reload the page and enter the same password, and it boots. This was seen on an empty save/ folder, and nothing was lost. This is tracked as CHORE-50 in Agents/Roadmap.md.

Docker

This fork builds from source with Docker. It uses its own project, container and volume names (risutanium and risutanium-save), so it does not touch an upstream Docker install. To bring your data over, make a .bin backup on upstream and load it here, as described in Migrating from upstream.

1. Clone this repository.
2. From the repo root, build and start it:

   docker compose up -d --build
   

3. Open http://localhost:6001.

The image is built from the Dockerfile in this repo (base image node:24-slim). The build needs Docker with BuildKit, because the Dockerfile uses RUN --mount=type=cache. The save lives in the risutanium-save volume, which Docker names risutanium_risutanium-save (the project name plus the volume name). The Node server problems above apply to this container as well, so use localhost.

Upstream's compose file also maps host port 6001, so this container and an upstream one cannot run at the same time. To run both, change the left-hand number of 6001:6001 under ports: in one of the two compose files.

The legal-documents notice in a Docker build

The Docker build has the flag on by default, so the image shows the app and not the legal-documents notice. The default is ARG VITE_RISU_LEGAL_CONFIGURED=TRUE in the Dockerfile, because .dockerignore keeps the repository's .env files out of the build context. docker-compose.yml passes ${VITE_RISU_LEGAL_CONFIGURED-TRUE}, so an unset variable becomes TRUE.

The value is baked into the frontend when the image is built, so opting out has to happen at build time. Setting it on a running container does nothing. To opt out, set it to an empty value in the shell that runs docker compose up -d --build or docker compose build:

# bash
VITE_RISU_LEGAL_CONFIGURED= docker compose up -d --build

# plain docker
docker build --build-arg VITE_RISU_LEGAL_CONFIGURED= .

Or put VITE_RISU_LEGAL_CONFIGURED= in your own .env file next to docker-compose.yml, which works from any shell. Compose reads that file, and .env is in .gitignore, so it stays yours. With an empty value the notice replaces the app.

Credits

The home-screen logo uses NanumSquare Neo by NAVER (designed by Sandoll), licensed under the SIL Open Font License 1.1. The font file and its full license are in src/etc/fonts/NanumSquareNeo/.

이 프로그램에는 네이버에서 제공한 나눔글꼴이 적용되어 있습니다.