BongoCat: a cross-platform desktop pet that reacts to your keyboard, mouse and gamepad

The problem BongoCat solves, and who actually wants it

The original Bongo-Cat-Mver by MMmmmoko is the reference point here. The README's development background section says it was loved for its cat interaction but supported Windows only, and that the author, a macOS user, wanted the same thing on their own machine. BongoCat is that port, widened by Tauri to macOS, Windows and Linux (x11).

So the audience is narrow and specific: people who keep a small animated character on screen and want it to move because they moved, not because a timer fired. The README lists the behaviours plainly. Keyboard, mouse or gamepad operations trigger the matching animation. Models can be imported. The app runs offline and, per the README, collects no user data. That last point matters more than it sounds, because a desktop pet sits on top of everything you do and could observe all of it.

If you want a mascot that idles on a loop, this is more machinery than you need. The value is in the input-to-animation link, and if you do not want that link, a GIF overlay is cheaper.

How the input-to-animation pipeline is put together

The stack is visible in the repository layout. The frontend is Vue 3 with Pinia for state, PixiJS and easy-live2d for rendering, and vue-i18n for localisation. The shell is Tauri 2, with the Rust side living in src-tauri/ and declared as a workspace member in Cargo.toml. The release profile there sets lto = true, codegen-units = 1, panic = "abort" and strip = true, which is a size-and-speed profile rather than a debug-friendly one.

Input capture is not a single cross-platform library. Cargo.toml pulls in the windows crate with Win32_Foundation, Win32_Security, Win32_System_Threading and Win32_UI_WindowsAndMessaging features, so Windows input handling is native. The workspace also depends on tauri-nspanel from a git branch, which is a macOS panel library, and on two local plugins, tauri-plugin-custom-window and tauri-plugin-admin-status. That last one is telling: on some platforms, reading global input can require elevated privileges, and the project appears to model that state rather than hide it.

The frontend side gets a long list of Tauri plugins, including plugin-global-shortcut, plugin-autostart, plugin-updater, plugin-os and plugin-log. The presence of an updater plugin is why release cadence matters to you as an operator, and the presence of plugin-clipboard-manager and plugin-dialog explains how model import is likely wired. The README does not document the event schema between the Rust capture layer and the Vue renderer, so if you plan to extend it, read src-tauri/ rather than the README.

Installing BongoCat from GitHub Releases and running it once

The README points at two download locations: a Quark netdisk share and GitHub Releases. It also links a download guide at .github/DOWNLOAD_GUIDE.md for people who are unsure which artefact to take. There is no package-manager instruction in the README, so the honest answer is that you fetch a release asset rather than run an install command.

Once you have the binary for your platform, the first real use is importing a model. The README says custom models are supported and points to the Awesome-BongoCat repository as a place to find and share them. If you are migrating from Bongo-Cat-Mver, the README names an online conversion tool at bongocat.vteamer.cc that rewrites those models into a BongoCat-compatible format.

If you want to build from source instead of downloading, the repository is a pnpm project. package.json sets a preinstall hook that runs npx only-allow pnpm, so npm and yarn are rejected before anything else happens:

pnpm install
pnpm tauri dev

The dev script is not plain vite. package.json defines dev as run-s build:icon dev:vite, and build:icon runs tsx scripts/buildIcon.ts, so the icon generation step is part of the normal development loop. A release build goes through pnpm build, which runs every build:* script in sequence. The README does not document a rollback path for the updater plugin, so treat upgrades as one-way until you have checked the release notes for the version you are moving to.

Where BongoCat is the wrong tool

Linux support is x11 only. The README states this twice, in the platform table and in the feature list. On a Wayland session, the input capture path this app relies on is not the one it was built against, and the project makes no claim of support. That is a hard boundary, not a rough edge, and it rules the app out for a large share of current Linux desktops.

The second limitation is privilege. The workspace includes tauri-plugin-admin-status, and on Windows the input path uses Win32 security and threading APIs. Global input capture is exactly the kind of capability that operating systems restrict, and macOS in particular gates it behind accessibility permissions, which is why the dependency list carries tauri-plugin-macos-permissions-api. Expect a permissions prompt, and expect the app to be partly non-functional if you decline it. The README does not describe the failure mode when permission is refused.

Third, there is no documented plugin API. The related searches include "bongocat obs plugin" and "how to install bongo cat plugin obs", but the README describes no OBS integration and no extension interface. Nothing in the repository layout suggests a published plugin surface either. If your goal is to drive an OBS overlay from your input, this project does not advertise that capability, and assuming it exists would be a mistake.

BongoCat against Bongo-Cat-Mver, its own ancestor

The obvious alternative is the project this one was derived from. MMmmmoko's Bongo-Cat-Mver is Windows-only, and that single fact changes the decision for everyone. On Windows, both are options, and the difference is not features but provenance: Bongo-Cat-Mver is the original model format and interaction design, while BongoCat is a reimplementation on Tauri with Vue and Live2D rendering.

That reimplementation buys three things. Cross-platform reach, since BongoCat adds macOS and Linux (x11). A model conversion path, because the README points at an online converter for Bongo-Cat-Mver models, which implies the formats are not directly interchangeable. And a different extension story, since BongoCat is a Tauri app with a Vue frontend rather than whatever the original used.

It also costs something. Bongo-Cat-Mver has a longer history on its single platform, and if you are a Windows user with a model you like, migrating means running it through the converter first. The README does not promise that every model survives conversion. If you are on Windows and already happy, there is no compelling reason to switch; if you are on macOS or x11 Linux, BongoCat is the only one of the two that applies.

Maintenance, licence and the cost of staying current

The repository is not archived, and the last push was on 2026-09-20, one day before this was written. Release history shows v0.9.0 on 2025-12-24, v1.0.0 on 2026-04-08 and v1.1.0 on 2026-04-20, with package.json also sitting at 1.1.0. So the project is moving, but the tagged releases are months apart while commits continue. That gap is the practical upgrade question: the updater plugin in the dependency list means the app can pull new versions, yet the release notes are the only place that would tell you what changed, and the README does not describe a rollback path once an update lands.

Licensing is MIT, per the LICENSE file and the repository metadata. MIT is permissive: you can use, modify and redistribute the code, including commercially, provided the copyright notice and permission notice travel with it. That has one consequence worth naming for anyone shipping a build to other people. The workspace also depends on tauri-nspanel from a git branch rather than a published version, and on two in-repo plugins. Those carry their own terms, and the LICENSE file at the repository root covers this project, not necessarily every transitive dependency. That is a packaging question for your own legal review, not something this article can settle.

The maintenance cost on your side is low if you use the app as shipped and higher if you build it. Building means pnpm, a Rust toolchain and a Tauri build, and the release profile in Cargo.toml disables debug assertions and overflow checks, so a source build is not a debugging build.

Editorial conclusion

Adopt BongoCat if you want a low-commitment desktop companion that mirrors your actual typing and clicking, and you are on macOS, Windows or Linux under x11. Skip it on Wayland sessions, where the README claims no support, and skip it if you need a documented plugin API or OBS integration, because the README describes neither. Before installing, open the download guide in .github/DOWNLOAD_GUIDE.md and match the release asset to your platform, then confirm the MIT licence in LICENSE suits how you plan to redistribute it.

Frequently asked questions

Official sources

1. ayangweb/BongoCat on GitHub
2. License: MIT
3. Project website
4. README
5. Releases