/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

moeru-ai/airi

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:45:08.076Z

1mo ago

moeru-ai/airi

Project AIRI is a large, active open source repo for a self-hosted AI virtual character companion. It targets web, macOS, Windows, and includes Rust, Node.js/TypeScript, and documentation infrastructure. The repo is highly popular and recently active, with 36,592 stars, 3,626 forks, and a fresh release track at v0.9.0-alpha.36.

Loading tags...

Stars36,592

Forks3,626

Default branchmain

Last pushed2026-03-30T15:23:01Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want a Vietnam-focused, student-oriented AIRI derivative with its own product identity and UX direction. Choose upstream if you want maximum feature coverage, easier upgrades, and lower maintenance risk.

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.

Fork comparison

zennomi/sanbaka

38/100

stale

significant_divergence

Choose this fork if you want a Vietnam-focused, student-oriented AIRI derivative with its own product identity and UX direction. Choose upstream if you want maximum feature coverage, easier upgrades, and lower maintenance risk.

Likely purpose

Adapt AIRI into a localized, opinionated companion experience with custom product messaging, UI/workflow tweaks, and fork-specific packaging for a narrower audience.

Best for

Vietnamese-speaking teams building a student-focused companion app.; Developers who want a strongly branded, opinionated fork instead of upstream AIRI.; Groups willing to own long-term maintenance in exchange for localized product direction.; People prioritizing UI/product tweaks over staying close to upstream release cadence.

Additional features

Localized Vietnamese product identity and messaging for student audiences.
Fork-specific UI/workflow changes around the stage UI, including chat action menu and PWA update prompts.
Pocket/mobile and desktop-adjacent maintenance changes, including Kotlin migration work for Android MainActivity.
Custom assistant behavior or game logic changes in the Minecraft-related codepath.
Repository-level maintenance and packaging updates, including dependency lockfile churn and release artifact tracking.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

The fork is 200 commits behind upstream, so it likely misses recent AIRI releases and active upstream fixes.
Minecraft-related cognitive logic appears to have been removed or heavily rewritten in `services/minecraft/src/cognitive/conscious/brain.ts`.
Upstream database/migration state in the server appears to have diverged, with multiple Drizzle snapshot files deleted or replaced.
Some upstream package and workspace structure is materially out of sync, making upgrades and reuse harder than on main.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Clear localization and product focus for a specific user community.
Large amount of fork-specific work suggests it is not just a cosmetic rename.
Recent changes indicate active attention to UX polish and mobile/PWA usability.
Could be a better starting point for teams that want an opinionated companion product rather than a generic platform.

Risks

Significant upstream drift raises merge and maintenance cost.
Likely slower access to upstream bug fixes and release improvements.
Removed or rewritten core subsystems may make future feature parity difficult.
The narrower branding and audience may reduce flexibility if you want a general-purpose AIRI deployment.