Sign in
The first screen you meet. You sign in with a Google account, and nothing else in the app is reachable until you do. The account is what connects this machine to your subscription and to your saved settings.
LoL Sensei runs as a small Windows app next to the League client. It follows what is happening in your game and shows champion select notes, item and rune suggestions, and a compact overlay while you play.
The client is in early access: it is unfinished, parts of it will change, and some of it will break. This page walks through every screen, so you can see how it works before it is available to install.
The app is a single window, 800 by 820 pixels, with a sidebar. Two of its tabs only appear when they have something to show: champion select shows up while you are drafting, and the in-game tab shows up while a match is running. The app switches to them on its own, so you do not have to click anything while you are busy.
The first screen you meet. You sign in with a Google account, and nothing else in the app is reachable until you do. The account is what connects this machine to your subscription and to your saved settings.
The second screen, and the second stop. It sets out what the app reads from your League client and asks you to agree before anything is read. If no consent is recorded, the app goes no further.
The tab the app opens on. It tells you whether the League client has been found and whether the app is talking to it, keeps a running log of what happened during your last champion select, and holds the cards that explain the early access build and the first steps.
Appears in the sidebar only while you are drafting. It lists your team as the picks come in, scores how well they fit together, shows each player's rank and recent champions, and gives notes on the champion you are about to play: a suggested rune page you can import into the League client with one click, an ability order, and a drawer with counter notes on the enemy picks. Picks and bans come from the League client itself, the counter notes come from our written champion guides, the rank and history information comes from Riot's public API, and the champion advice comes from an AI model.
Appears only while a match is running. At the top are the item suggestions for the build you are putting together right now. Below is a grid with the ten players in the match, their scores and the items they have shown so far. The live numbers come from the data feed the game publishes on your own machine, and the item advice is computed on our server.
Your profile and your match history, built from Riot's public API through our server. It is a reading view: nothing on this tab changes anything in your account or in the game.
Your account and subscription, your credit balance, your Riot region, and the overlay options: the keyboard shortcut that hides and shows it, and where on screen it sits. At the bottom you will find the installed version number, which is the one to quote when you report a problem, and the notice that we are not affiliated with Riot Games.
The overlay is a separate window that floats over the game. It is small, has no border, stays out of the taskbar and out of Alt-Tab, and is built so that it never takes focus away from League of Legends. A keyboard shortcut hides it and brings it back. There are two of them: one during champion select, one during the match.
It shows the picks and bans as the League client reports them, the AI notes on the champion you are about to play, and the matchup cards from our written guides. It is the same material as the champion select tab, in a form you can read without leaving the client.
It comes in three sizes and you cycle through them mid-game, either with the keyboard shortcut or by clicking the overlay itself. The smallest is a single strip: your gold, your gold difference, one suggested item. The middle one adds the next item in your build and a note on your matchup. The largest adds the full build order, the AI item notes, a read of how the game opened, the biggest threat on the enemy team, matchup advice, professional builds, and how your own game is going.
While a match is running, League of Legends publishes a data feed on your own machine, at 127.0.0.1 on port 2999. Any program on that machine can read it and no password is involved. That feed is where the overlay gets the clock and the game mode, your gold, level and champion stats, your six item slots, the ten players with their kills, deaths, assists, creep score, vision score and visible items, and the public events such as a dragon or a baron going down. The objective timers are arithmetic on those events: something dies, the clock starts. The item advice itself is worked out on our server and sent back to the app.
The desktop client is on its way: it cannot be downloaded yet, and in the meantime this page is here to show what it looks like and what it does.
Coming soonA 64-bit Windows machine with League of Legends installed on it. There is no macOS build and no Linux build. The current version is 1.0.111.
The champion notes in champion select, the item suggestions during a match and the rune pages are written by a large language model. Models get things wrong. They can suggest an item that no longer exists on the current patch, misjudge a matchup, or state something confidently that is simply not true. Read them as an opinion, not as a rule, and if the advice disagrees with what you can see on your own screen, trust your screen.
No person checks that advice before it reaches you. There is no editorial pass over what the model writes inside the app, so treat anything surprising as something to verify rather than something to follow.
Not everything in the app is generated. Your profile and match history are numbers from Riot's public API. The objective timers are arithmetic on the events the game publishes. The counter cards, the matchup notes and the synergy notes are read out of champion guides that were written in advance, not produced on the spot. None of this passes through a model, and we do not label it as if it did.
The app talks to two things on your own machine, and both are interfaces the game itself offers. The first is the League client, which it only reads from: the phase you are in, the champion select session, your lobby, your summoner details, your region and your rune pages. The second is the match data feed on 127.0.0.1 port 2999, described in the overlay section above. It writes in two places only: the rune page it imports when you press the button, and the item set file described below.
Anything that needs Riot's public web API, such as your profile, your match history and other players' ranks, is requested by our server rather than by the app on your machine. Our Riot API key lives on the server and is never shipped inside the client. Your account is a Google sign-in, and the answer you give on the consent screen is recorded so the app knows you gave it.
The app writes one file of its own inside the League folder: an item set called LoLSensei.json, placed in the recommended items folder of the champion it applies to, in the format the game documents for item sets. It adds a file alongside the game's own; it does not modify or replace anything the game installed.
This is an early access build and it has rough edges. If it crashes, hangs or shows you something that makes no sense, write to support@lolsensei.com with the version number from the bottom of the settings page and what you were doing at the time. Reports from testers are the reason this build exists.
LoL Sensei isn't endorsed by Riot Games and doesn't reflect the views or opinions of Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games, and all associated properties are trademarks or registered trademarks of Riot Games, Inc.