League Akari: an Electron LeagueClient toolkit built on the LCU API

What League Akari is and who it is for

League Akari is a desktop application for the League of Legends client. The README describes it as "A League of Legends client toolkit based on the LCU API", and the repository is written in TypeScript with Electron as the runtime, which is visible from the electron-vite configuration files and the electron-builder.yml at the top level. The package name is league-akari and the current version string in package.json is 1.5.2-beta.

The audience is narrow and specific. You need a running League client, an account on a Riot-operated region, and a willingness to run third-party software alongside it. The README states that most Riot-operated regions are supported and that Tencent-operated servers are not, which rules out a large part of the player base before installation even starts. It is not a game modification, not a script that plays for you, and not a mobile companion. It is a Windows or macOS program that talks to the local client process.

The repository has been pushed to recently, on 2026-09-09, and it is not archived. The release list, however, shows only dev prereleases with names like "League Akari Dev Prerelease #76 (5109b2f)". That naming matters if you expect a stable channel: the recent releases are prerelease builds, not tagged stable versions.

How the LCU API integration actually works

The mechanism is the League Client Update API, usually shortened to LCU. The client exposes a local HTTP and WebSocket interface while it runs, and the README's disclaimer confirms this is the basis: "This software is a tool developed based on Riot's League Client Update (LCU) API." It also states the software "does not use intrusive techniques and theoretically does not directly interfere with or modify game data."

That sentence is the whole architecture in miniature. League Akari reads from and issues requests against the client's own API surface rather than injecting into the game process. The dependency list supports this reading: ws is present for WebSocket handling, axios-retry for HTTP requests with retries, zod for schema validation of incoming payloads, and mobx for state management on the front end. The data flow is client process to local API to League Akari to its UI.

Two dependencies hint at what sits underneath the UI. better-sqlite3 and typeorm together suggest a local database, most likely for caching or persisting settings and match-related data rather than for anything server-side. luaparse is a Lua parser, and the League client's own configuration files are Lua, so that dependency points at reading or writing client-side configuration. The README does not document what each module does, so treat those as inferences from the dependency list rather than documented behaviour.

The README credits several projects as inspiration, including Pengu Loader, a JavaScript plugin loader for the LoL client, and Seraphine, which it says provided "integration approaches and insights into combining multiple tools." That is a useful signal about the design lineage: League Akari sits in the same family as LCU-adjacent client tools rather than in the game-overlay family.

Installing League Akari and running it for the first time

The README does not document a package-manager install. It points at GitHub Releases: "Download the latest Windows or macOS build from GitHub Releases." There is no npm or Homebrew command to copy, and inventing one would be wrong. What follows is the developer path from the README's Development section, which is the only install procedure the repository actually documents.

The project uses Node.js 24 and Yarn 4. The README says to enable Corepack before installing dependencies, then install and start the dev server:

corepack enable
yarn install --immutable
yarn dev

The first command activates the Yarn version pinned in the repository. The second installs dependencies in immutable mode, which means it fails rather than rewrites the lockfile if anything drifts. The third launches the Electron app in development with watch mode enabled, since the package.json dev script is electron-vite dev --watch -- --inspect. You should see the Electron window open and attach to the running League client; the README does not describe what the first screen looks like, so do not expect a documented onboarding flow.

The README lists the other commands you are likely to need:

yarn typecheck
yarn test
yarn build
yarn build:win
yarn build:mac

yarn typecheck runs two passes, one for the Node side and one for the web side, using tsc and vue-tsc respectively. yarn test runs vitest once. yarn build produces the production bundle, and the platform-specific commands wrap electron-builder to produce distributable packages. If you only want to use the tool rather than build it, skip all of this and take the release binary.

One platform note from the README: "Administrator privileges are not required. On Windows, some native shortcuts, overlays, and client-window utilities require administrator privileges." So the base application runs unprivileged, and only specific Windows features ask for elevation.

The Tencent server gap and the anti-cheat caveat

The hardest limitation is regional. The README states plainly that most Riot-operated regions are supported and that Tencent-operated servers are not supported. If your account lives on a Tencent-operated server, League Akari is not the tool for you, and no configuration will change that. This is a hard boundary, not a missing feature.

The second limitation is the one the project itself raises in its disclaimer. The README notes "potential compatibility issues or risks associated with game updates or anti-cheat systems" and states that the developer is not responsible for consequences "such as account bans or data loss" resulting from use of the software. It also states the application is not officially supported or endorsed by Riot Games and that use "may violate the game's terms of service." That is unusually direct for a project README, and it should be read as the maintainer telling you the risk is yours.

There is a practical failure mode that follows from the architecture. Because everything depends on the LCU API exposed by a running client, a client update can change endpoints or payload shapes and break features until League Akari is updated to match. The disclaimer's mention of compatibility issues with game updates is exactly this. The repository does not document a version-compatibility matrix, so there is no published way to check whether a given League client build works with a given League Akari build before you try it.

Finally, the release channel is a limitation for cautious users. The recent releases are dev prereleases. If you want a stable, versioned release, the README does not point you at one.

How League Akari differs from Pengu Loader and Seraphine

The README names its inspirations, which makes comparison straightforward. Pengu Loader is described there as "The ultimate JavaScript plugin loader, build your unmatched LoL Client." That is a different shape of tool. Pengu Loader loads JavaScript plugins into the client itself, so the extension point is the client's own runtime. League Akari is a separate Electron process that talks to the client over the LCU API. If you want to write plugins that live inside the client, Pengu Loader is the closer fit; if you want a standalone desktop application with its own UI, League Akari's model is the one you want.

Seraphine is credited with providing "integration approaches and insights into combining multiple tools." That phrasing suggests Seraphine is also a multi-feature client companion rather than a single-purpose utility. The meaningful difference for a reader is packaging and platform: League Akari ships Windows and macOS builds through GitHub Releases and is written in TypeScript on Electron. The README does not describe Seraphine's stack, so a direct technical comparison beyond that is not supported by the material.

The other credited projects are narrower. fix-lcu-window addressed abnormal client window sizing, and LeaguePrank is credited with inspiring "playful and humorous features." Those are single concerns that League Akari appears to fold into a broader toolkit, which is the point of calling itself all-in-one.

Maintenance, licensing and what an upgrade costs you

The repository is not archived and the last push was on 2026-09-09. That is recent enough that the codebase is moving, but the published releases around that date are dev prereleases, so the practical upgrade path is to follow prerelease builds rather than wait for stable tags. The README does not document a rollback procedure or a downgrade path, so if a prerelease breaks something you rely on, the repository is silent on how to get back to a working state. Plan for that by keeping the previous build you downloaded.

The licence is MIT, which is permissive: you can use, modify and redistribute the code, including in closed-source form, provided the licence and copyright notice are preserved. League Akari's own MIT licence does not extend to Riot's assets or to the League client itself. The README is explicit that "All rights are reserved by Riot Games" and that the application is not endorsed by Riot. Nothing in the MIT grant changes the game's terms of service, and the disclaimer places responsibility for bans or data loss on the user. That is a statement of risk allocation, not legal advice.

For contributors, the repository carries AGENTS.md, CLAUDE.md, PR_REQUIREMENTS.md and a specs directory, which indicates there are documented expectations for pull requests. The README says code contributions are welcome and asks bug reporters to include enough detail to reproduce the problem. The repository also runs typecheck and vitest in its own scripts, so a contribution that fails either will be caught.

Editorial conclusion

Adopt League Akari if you play on a Riot-operated region, want a desktop companion to the League client, and accept that the tool talks to the LCU API under Riot's terms of service. Do not adopt it if you play on a Tencent-operated server, since the README states those are not supported, or if you need a stable release channel rather than the dev prereleases the repository currently publishes. Before installing, verify which build matches your platform on the GitHub Releases page and read the disclaimer in the README about anti-cheat and account risk.

Frequently asked questions

Official sources

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