glitchless_list_games | Which games report to the server, with their versions and environments; signed in to a workspace, every game in it with its client token |
glitchless_sign_in | Connect to a Glitchless Cloud workspace: a link and a code for the person to approve |
glitchless_create_game | A new game in the workspace, with its client token and intake URL (a name already there returns that game); with engine, or files (what's in the game's folder), also the steps that add Glitchless to the game's code for its engine, for a new game (name) or one already there (game): the instrument skill, for an agent without it; demo: true makes the demo game (a week of sample play); rename (with game) renames one instead, its client token, service and data unchanged; delete (with game, and the game's name again) deletes it and everything Glitchless keeps for it, for good: a key with delete_games (off unless an Owner or Admin ticked it), and when two games share the name, game is its id; the client token is refused from then on |
glitchless_share_links | A read-only link to one board page, for a dev log, Discord or a game's "Live stats" link (page), or with claim: true a claim link that hands a game the team made to its creator, who moves it into their own workspace; lists them, and revokes one (revoke) |
glitchless_triage | The headline numbers (sessions, players, crash-free sessions, frame time, rage quits), then ranked findings: stutter per level and what it correlates with, leaks, top errors, difficulty spikes. Start here |
glitchless_mark_known | Mark a finding the game's owner accepts as known, so the weekly summary stops listing it (triage shows it last, with the note); with player or session instead, the team's own play, read as testers in every tool; clear: true removes the mark |
glitchless_resolve_error | Resolve an error issue the game's owner fixed or accepts: hidden from the Errors page, triage and the weekly summary until it fires again in a newer version (any_version: any); clear: true unresolves it |
glitchless_alerts | A game's alerts: where they go, which rules are on, the weekly summary, the env, and the last sends; glitchless_set_alerts turns rules, the weekly summary and email on or off, sets the env, removes the webhook and sends a test (a webhook URL is added in Settings → Alerts) |
glitchless_performance | Frame time per level, with draw calls, geometry counts and game gauges |
glitchless_get_error | One error issue, with its stack and the gameplay before it |
glitchless_player_funnel | Per level: starts, completions, deaths and their causes, disconnects, rage quits; split by what describes the attempt (tier, party size, class), runs per level, and retention; with hotspots, where players die on a level, in a zone or anywhere in the game (a hub with no levels), clustered in world coordinates |
glitchless_events | The game's own events (whatever it sends with track, and the streams it counts with count): counts, attribute breakdowns, rates, distributions and funnels, and the session properties it sets |
glitchless_dashboard | The game's dashboard: its pages, and one board's panels with their numbers; with guide: true, how to design one for the game (the dashboard skill, for an agent without it) |
glitchless_set_dashboard | Save the game's pages: boards of panels in its own words, and the built-in views it keeps; and, each alone if you like, the boards' accent, logo and banner (the header behind each board's title) and a level's, zone's or the whole game's heatmap background (a picture from a file or base64 and its world bounds; over the hosted server a file is answered with a 10-minute, single-use upload link to send it to with one curl). Needs a key with the dashboard scope |
glitchless_compare_versions | Two or more versions side by side, in the game's own stats first, to confirm a fix with real players |
glitchless_session | One play session in detail, with its whole event timeline |
glitchless_bug_reports | Bug reports players sent from inside the game: their notes, levels, positions and sessions, and one report's screenshot when asked |
glitchless_store | For a game connected to a store (Glitchless Cloud: Steam, Google Play, the App Store, Roblox, itch.io, the Microsoft Store): what players wrote there, by store, build or version, sentiment, topic (stutter, lag, fps, freeze, crash), device and, on Steam, Steam Deck, each build with the frame-time p95 and crash-free sessions measured on it; with show: "vitals", what Google Play (slow rendering, crash and ANR rates, the slowest devices and GPUs) or the App Store (hang rate, launch time, animation hitches, hang signatures) or Roblox (crash rate and frame rate by place version and platform, and its retention) or the Microsoft Store (crash and hang rates by package version from Windows error reporting, and the heaviest failures; not Xbox consoles) measured of each version, next to what Glitchless measured, and where the two disagree; with show: "sales", what the store counted by day: Steam's units, returns and wishlists, itch.io's page views, downloads and purchases next to the browser plays Glitchless measured on itch.io, or the Microsoft Store's acquisitions by kind and add-ons |
glitchless_revenue | For a game connected to RevenueCat, its own Stripe account, Roblox or itch.io (Glitchless Cloud; source picks one, else each): its real revenue by day and revenue per player measured. RevenueCat's (production purchases only): installs (new customers) and active users, MRR, active subscriptions and trials, and revenue by version where RevenueCat splits it. Stripe's: refunds, disputes, fees and net, new paying customers, revenue by product, and by version and platform for purchases the game tied to a session. Roblox's: Robux earned (and what they'd be worth through DevEx), paying users, daily active and new users, and D1, D7 and D30 retention. itch.io's: its earnings by day, from the first sync (itch.io gives a total only). All next to the sessions, players and new players Glitchless measured and what the game's own purchase events add up to |
glitchless_match | A multiplayer game's matches (the worst by lag or disconnects on request), or one match from every side, 30 seconds at a time: each player's ping, frame time and outcome, the server's ticks, and whether the whole lobby lagged at once (the server) or one player did (their connection) |
glitchless_network | Ping, lag (play over 150 ms), packet loss and disconnects by level, version, platform, kind of connection and region, with the worst matches and the network findings |
glitchless_servers | A game's dedicated servers in server mode: servers running now and their players, tick time against its budget by players connected, map and version, crashes with the matches they ended, and memory that climbs. Every other tool reads them with service <game>.server |
glitchless_playtest | The game's autoplay bot plays it and the run is compared with a saved baseline (glitchless-playtest): a Unity, Godot, Unreal or GameMaker build from its command, a Roblox game in the open Roblox Studio (engine: "roblox", over Studio's MCP server), or a web game in Chrome (needs Playwright in the game project). With check_url, a game check: bots play any web game someone posted (an itch.io page, github.io, Vercel), with nothing installed in it, on a desktop and a throttled phone, and make a report, a dashboard for that game and, on Glitchless Cloud, an unlisted share link to send its maker |
glitchless_deck | Build the game, send it to the paired Steam Deck, add it to the Deck's library and optionally start it (glitchless-deck; pair once with npx glitchless-deck pair); with measure: true, measure a Unity, Godot or Unreal build there and compare it with a saved run |