AI workers for game studios.Starting with repeatable QA.
Put a QA worker on the checks slowing your next release. BugHunter learns your game, runs on real devices, and returns gameplay evidence. We help you get started; your team runs it, with support when you need it.
Send us a link to your game. We'll prepare a demo around it.
Your next build still needs these checks.
Give BugHunter the repeatable work: player flows, purchase checks, and fix verification. Your QA team reviews the results and focuses on the next risk.
Replay critical player flows
Check tutorials, progression, shops, and live-event journeys on the next build, with the observed result and gameplay recording for review.
Retest the fix
Replay the issue on the replacement build and review what changed, with the original finding and new build connected.
Keep checks moving overnight
Add execution around release deadlines without assigning every run to someone on your team.
- Choose the build and checks
- BugHunter runs the game
- Review the evidence
- Fix and retest
See the build, the check, the observed result, and the gameplay behind the finding.
Your team runs the workflow. BugHunter executes the checks. NodeMori helps you get started.
See the work behind the report
Follow the task, watch the gameplay, and review what happened. A useful QA result connects the build, test steps, expected behavior, and evidence so your team can decide what needs attention.
BugHunter explores real builds like a player, catches regressions and edge cases, and packages each issue into a report built around gameplay video and the assigned task. Additional diagnostics such as logs and reproduction steps depend on the run and setup.
Each result starts from the agreed task and the supported build it ran on, so the check is easy to place.
Watch the agent move through the flow and see what happened, with video your team can replay.
Each finding pairs the assigned task and expected behavior with gameplay evidence. Reproduction detail and logs depend on the run and setup.
Seen at GDC 2025 and GDC 2026
Refined with direct feedback from studios and game industry teams.
Your QA worker. Your workflow.
Start with onboarding for your game, then choose how much support you need.
Run it with your team
Select builds and checks, start runs, review findings, and request retests.
Add hands-on support
Get help preparing checks, maintaining the workflow, or running an agreed batch when your team needs extra support.
Add support for a busy release or make it part of your ongoing workflow.
Each build adds to your game knowledge.
BugHunter combines your game instructions with gameplay, prior runs, and QA feedback. Reuse approved checks, useful paths, and confirmed findings on the next build.
Keep what your team has learned as the game changes.
Learns the paths
How to reach the tutorial step, shop, event, or player state being checked.
Learns what matters
Expected behavior and feedback on which findings deserve attention.
Reuses the work
Prepared checks, issue history, and earlier evidence support later runs.
- Run
- Record experience
- Apply QA feedback
- Update game knowledge
- Reuse it
Your team reviews each run and approves what becomes reusable game knowledge.
QA accepts a finding in a reward-claim flow. On a later build, BugHunter rechecks that path using the approved expectation and earlier context.
QA knowledge that stays with your studio.
Approved tests, reproduction paths, and build history remain part of the workflow as your team grows and changes.
See what builds experienceA clearer view of each submitted build.
Run agreed checks on a studio's build and bring the results into your milestone review. See what was tested, what needs attention, and which fixes were verified. Start with one title, then extend the workflow to the next.
A partner submits a new milestone build
A clear view of what was tested, what needs attention, and what remains unchecked.
The developer reports a fix
Evidence that connects the issue to the observed retest result.
Release calendars collide
Per-title results and outstanding work for the next production review.
A publisher receives an authorized summary for the agreed title and build. Reviewing a build does not grant access to a studio's private gameplay or training data for other titles.
The workflow
From your build to the next check.
Assign a check, review what happened, fix the build, and run it again.
- 01
Connect your game
Share the build, game context, and first checks during onboarding.
Nodemori helps your team configure the first run.
- 02
Assign the work
Your team chooses the build, task, and expected result.
Your team sets priorities.
- 03
Run and review
BugHunter executes the checks; your team reviews the evidence.
Your QA team accepts, rejects, or merges findings.
- 04
Fix in your workflow
Send findings to Jira or your tracker and update the build.
Your developers own the code changes.
- 05
Check again
Rerun the check and carry accepted knowledge into the next build.
Your team starts the retest.
Your QA lead approves findings. Your developers own fixes and release decisions.
Use Unity or Unreal and Jira or your tracker. You can also request runs through an optional MCP connection.
Task: Complete the tutorial and verify that its reward is granted once.
BugHunter records the tutorial and reward claim on the agreed build and test account. If the visible result cannot establish whether the reward was credited once, the check needs more evidence.
After a fix, rerun the check. If the design changes, QA approves the new expectation and baseline.
A result your QA and engineering teams can use
Review the build, starting state, expected result, and gameplay recording. Logs or internal state are included where connected.
- Outcome: pass, fail, blocked, or not run. Release approval stays with your team.
- QA decision: pending, accepted, rejected, or merged, set by your team.
- Retest reuses or revises the expectation on the fixed build.
Owners for each step, the four QA tasks, and how findings reach your tools
Four QA tasks. One worker.
BugHunter takes on different QA jobs depending on what you need checked. Each task has a clear input and a clear output your team can review.
Task availability depends on the game and build. Your team sets the checks and accepts the results.
Scout
Understand the build
Explore a selected area and draft the mechanics, flows, and candidate checks for your team to review.
Learn more
Freeplay
Explore a goal
Follow an open-ended objective within a run limit and capture observations, blockers, and the path taken.
Learn more
Testcase
Check expected behavior
Execute approved steps and compare the observed result with the expected behavior on the current build.
Runs on the deterministic test-case capability shown in the product.
Learn moreRegression
Retest across builds
Repeat approved checks and accepted issue paths on a later build, using the relevant baseline.
Reuses the deterministic test-case execution on a later build.
Learn moreStart with your game
Begin with a demo on a supported build, move into a scoped workflow pilot, then keep the checks you rely on running as your game changes.
Game demo
Share your game and see one agreed task on a supported build. For a longer evaluation, apply for the free Guided Pilot Run.
Workflow pilot
A paid engagement for one repeatable QA workflow, including review and a follow-up run. We agree the deliverables, timing, and fixed fee in advance.
Ongoing QA
Keep agreed checks running across upcoming builds. Choose the execution capacity, support, review, and integration scope your team needs.
BugHunter extends your QA capacity for agreed, repeatable checks. It works alongside your QA team rather than replacing the judgment they bring.
Frequently asked questions
See it on your game. Then make it part of your team.
Send a game link and see BugHunter in action. We help you set up the product and get your team running. Add ongoing support whenever you need it.