moeru-ai/airi

Choose this fork if its added provider, localization, and onboarding changes match your needs and you are comfortable maintaining a long-lived, substantially diverged branch. If you want current AIRI behavior and active upstream features, upstream is the safer default.

Choose this fork if you want a more experimental, voice-centric AIRI variant and are comfortable maintaining a large divergence. Prefer upstream if you want the full current feature set, especially recent release, UI, PWA, server, and pocket work.

Choose this fork if you want AIRI as a customizable platform for provider/integration work and can tolerate merge debt. Choose upstream if you want the freshest release line and lower maintenance risk.

Choose this fork if you want a more customized, character-centric AIRI with sticker, onboarding, and chat-UX enhancements. Choose upstream if you want the broadest feature coverage and the easiest path to future updates.

Choose this fork if Unreal Engine integration, ModelScope, or the added localization/workflow tweaks matter more than staying current with upstream. Choose upstream instead if you want the latest AIRI release line, recent UI/server fixes, and lower maintenance burden.

Choose this fork if you want a customized AIRI deployment path with Cloudflare-focused operational changes and are willing to manage a major upstream delta. If you want the most current, low-friction AIRI experience, upstream is the safer choice.

Prefer this fork if you want a customized AIRI base with onboarding and runtime polish and you do not need the newest upstream release line. Prefer upstream if you care about staying current with the latest fixes, PWA/client work, and release-track changes.

Choose this fork if you want a customized AIRI product surface and can afford ongoing merge maintenance. Choose upstream instead if you want the newest AIRI fixes and the lowest upgrade risk.

Choose this fork only if its pocket/mobile and localization tweaks are the point. For most adopters, upstream is the safer base because this fork is far behind and likely missing later fixes and polished UI/runtime work.