Bugs reported
FireLab makes your game see any Fire TV model's GPU, in desktop Chrome, an emulator or the stick you have. Then its engine plays the game with the remote and shrinks every bug to the shortest key sequence. No Fire TV needed to start.
One click starts FireLab in a GitHub Codespace and opens the dashboard on a simulated TV. Free with a GitHub account, nothing to install.
firelab explore --package com.example.game --minutes 30Plays your game with the remote and shrinks every bug it finds.
"kind": "unexpected-exit", "severity": "major", "title": "Back quit the app", "device": "AFTMA08C15", "keys": ["menu", "up", "up", "up", "left", "right", "up", "back"], "shrunkFrom": 37, "repro": { "hits": 5, "runs": 5 }, "status": "confirmed"
Left: a real recording of the FireLab dashboard on a 1 GB Fire TV Stick running Firefly Lake. Right: a real finding from a Fire TV Stick 4K Plus.
| Tester | Screens | Deepest | Code |
|---|---|---|---|
| FireLab | 246 | 36 | 77 |
| Random | 82 | 17.5 | 50 |
| Monkey | 70 | 13.5 | 43 |
Medians of 4–5 runs in headless Chrome at the Fire TV viewport. Games and bugs written by FireLab's authors; p-values indicative.
Explore, focus checks, GPU checks, live performance and every-model verdicts, all over adb, with nothing to install on the Fire TV.
Firefly Lake on a 1 GB Fire TV Stick (3rd gen), recorded on 19 Oct 2026. The sweep finds the richest quality tier that holds 30 fps.
Verdicts are estimates. Two profiles are measured on real sticks (4K Plus, 3rd gen); the rest come from published specs and say so.
firelab uiDashboardMirror, remote, performance, console, test jobs and reports.
firelab mcpFor AI agents25 tools for Claude Code, Kiro, Cursor and VS Code.
firelab wrapWeb game to APKTurns a URL into a Fire TV app, no Gradle.
firelab labNo TV neededFire-TV-shaped emulators and a GitHub Action.
Every run writes a self-contained HTML report and Markdown for pull requests. No account, no upload.
Screenshot, shortest key sequence, reproduction rate and a replay command for every finding.
Coverage curves, a per-bug table and the statistics behind the numbers.
A verdict for each Fire TV model, with the reason and how sure it is.
# no Fire TV? test your web game in headless Chrome (Node 22+) npx -y firelab explore --driver browser --url http://localhost:8080/ # or watch the engine on a simulated game npx -y firelab demo # install it for a real Fire TV (needs adb) npm install -g firelab # your Fire TV: Developer options → ADB debugging firelab devices --scan --connect firelab doctor firelab ui firelab explore --package com.example.game
The step-by-step guide covers TV setup, getting your app on the TV, reading the report, performance, every-model checks, emulators and CI.
Add it to Claude Code (no clone needed):
Star FireLab so other Fire TV developers find it. Fork it, add your stick's measured profile, and send a pull request. Using it in your project? A credit line is all the MIT licence asks.
Tested with FireLab (https://github.com/AkilSaji/firelab), MIT.An open-source toolkit for testing apps and games on Fire TV and Android TV: a game-testing engine, a live dashboard, a CLI, an MCP server for AI agents, a performance library, every-model checks and Fire-TV-shaped emulators.
No. npm run demo runs the engine on a simulated game, firelab lab makes emulators shaped like real sticks, and web games can be tested in headless Chrome. A real stick gives the real numbers.
Native APKs get crash, ANR, exit, black-screen, frozen-picture and focus checks. Web apps in a debuggable WebView also get JavaScript errors, render-loop checks and focus from the page.
They're estimates from one device plus model profiles. Two profiles are measured on real hardware; the rest come from published specs and are marked as estimates. Test on the real device before you ship.
There is a Vega driver built from Amazon's documentation. It hasn't been run on a real Vega device yet.
Yes. MIT licensed, runs locally, no account and no telemetry.