Two signals, not one
PokerStars windows have to satisfy both halves of their definition: the title must match, and so must the window class. A window whose title says “No Limit Hold’em” but whose class is a browser is not a table and is left alone.
That matters more on PokerStars than elsewhere, because its table titles contain generic game names — “No Limit Hold’em”, “Pot Limit Omaha”, “Fixed Limit”. Those strings turn up in forum threads, training videos and spreadsheets. Requiring the class name is what stops your strategy PDF being tiled between two tables.
- Title must match
- “PokerStars”, a tournament table pattern, or a game name (No Limit Hold, Pot Limit Omaha, Fixed Limit)
- Class must also match
- PokerStarsTableFrameClass, GLFW30, or RationalEmbeddedBrowserWindowClass
- Both required
- Yes — a title match alone is not enough
Old client, new client, embedded windows
Three class names are accepted because PokerStars has shipped three kinds of table window. PokerStarsTableFrameClass is the long-standing native frame. GLFW30 appears on the newer rendering path. RationalEmbeddedBrowserWindowClass covers the embedded browser windows the client opens for parts of its interface.
You do not choose between them and there is nothing to configure: whichever your client produces is recognised. The same definition also knows that a window titled “lobby du tournoi” is a tournament waiting room rather than a live table, so it is not given a playing slot before the tournament starts.
- Lobby detected from
- lobby, cashier, my tournaments, pokerstars.fr, pokerstars.com, starscrm
- Tournament waiting room
- “lobby du tournoi” classified as waiting, not as a table
Layouts that hold across a session
Save a layout once and it is reapplied every time: tables in their slots, lobby on the side, your companion apps where you put them. Tables that open mid-session take the next free slot instead of landing on top of a table you are already in a hand on.
Hotkeys drive the whole thing without the mouse — cycle tables, move the focused window, reapply the layout — so a session with twelve tables does not become a window-dragging exercise.
When the client updates: Seatify Engine
Every detection rule above describes how the client behaves today. Rooms change their windows without notice, and historically that meant a broken layout until our next release.
Seatify Engine removes that wait. When a window stops being recognised, you open the Table Manager, point at it, and say what it is — a table, a lobby, a waiting room, a replayer or a railed table. The rule is saved on your machine and applies immediately.
You can then share it with one click. Once reviewed, it joins the set every installation can fetch, so the first player to hit a change fixes it for everyone. Downloaded rules are cryptographically signed and verified before being applied, and your own rules always outrank them. A shared rule carries the shape of a window title and nothing else: no tournament numbers, no stakes, no player names. It is available during the free trial too.
How it runs on your machine
Seatify Pro reads the properties Windows already exposes for every open window — its title, its class name, its size and position — and moves windows using the same Windows APIs any window manager uses. It never attaches to the poker client, never reads its memory, and never touches the cards or the action.
That boundary is deliberate and it is what keeps the tool inside room rules. A table manager that injected into the client would be both a security risk and a banning risk, and no amount of convenience is worth either.
