Papers
Topics
Authors
Recent
Search
2000 character limit reached

Build, Don't Play: Self-Improving LLM Research Agents Develop a Hearthstone Battlegrounds AI That Rivals Top Players

Published 24 Oct 2026 in cs.AI, cs.LG, and cs.MA | (2610.33845v1)

Abstract: Can LLM agents carry a hard real-world problem from raw data to a system that holds its own against people? We study this in Hearthstone Battlegrounds, an eight-player auto-battler with stochastic shops and battles, hidden information and nearly a thousand interacting cards. We present AutoTavern, a self-improving research system: specialised LLM research agents share a typed research memory, every claim passes verification gates, and live games close the loop, so the agents improve the simulator, opponents and policy and, from the same feedback, their own research process; a human sets goals and rules on ambiguous mechanics. In 20 days AutoTavern built TavernGym, the first faithful, full-content reproduction of the live game, and delivered 23 versions of TavernAgent, trained with PPO against opponents calibrated to real games. TavernAgent plays complete games on the live ladder by itself: its rating rose from 6,000 to about 15,000 and, on the public leaderboard's measure, its last 20 records average a placement of 1.60 with 80% first places, better than the server's ten highest-rated players on every statistic (2.34, 59%). TavernBench, 960 tasks in 40 scenarios, shows that the system the agents built is the strongest player: TavernAgent answers 91% of the play tasks against at most 63% for frontier LLMs, and decides in 0.03 s where they need up to 26 s; within the second a live turn allows, it keeps 90% and no LLM more than 26%. LLM agents build far better than they play. We will open-source TavernBench and TavernGym at https://github.com/MCG-NJU/AutoTavern.

Authors (2)

Summary

  • The paper demonstrates an LLM-based system, AutoTavern, that autonomously develops an AI for Hearthstone Battlegrounds, outperforming top players and playing competitively in a live game environment.
  • AutoTavern's primary method consists of specialized research roles within six types of LLM agents, coupled with a typed, versioned research memory, verification gates, and automated experimentation, noting the agent required 0.6% human input post initial 20 days creation.
  • The live-deployment loop in which TavernAgent was tested revealed 184 defects in the TavernGym simulator, highlighting the necessity of live game testing to maintain simulation fidelity, the system only needed 0.6% human involvement later on to input objectives or resolve ambiguous mechanics; this further supports the paper's central claim of autonomous system improvement.

Research objective and central claim

The paper investigates whether LLM-based research agents can autonomously carry a technically demanding game-AI project from environment construction to deployment in a live competitive setting. The target is Hearthstone Battlegrounds, an eight-player auto-battler characterized by stochastic shops and combat, partial observability, shared card pools, long-horizon credit assignment, and nearly one thousand interacting game objects. The central claim is deliberately divided into two parts: LLM agents can construct a highly capable specialized system through an iterative research process, but the same LLMs are substantially weaker when asked to make the system’s decisions directly.

The proposed system, AutoTavern, combines six specialized LLM research roles with a typed, versioned research memory, verification gates, automated experimentation, and a reality loop connecting simulation to live games. Over 20 days, the system registered approximately 10,000 experiments, produced 23 delivered TavernAgent versions, implemented 63,000 lines of Rust, and required 418 human messages, reported as 0.6% of all messages. The human remained responsible for setting objectives, resolving mechanics that could not be inferred unambiguously, and pressing the shortcut key corresponding to the agent’s selected action during live deployment. Thus, the claimed autonomy is substantial but not equivalent to unsupervised deployment.

The empirical contribution is supported by three artifacts: TavernGym, a full-content simulator for patch 36.6.3; TavernAgent, a PPO-trained policy operating through a transformer architecture; and TavernBench, a 960-task benchmark for evaluating Battlegrounds decision-making. The results are reported in “Build, Don't Play: Self-Improving LLM Research Agents Develop a Hearthstone Battlegrounds AI That Rivals Top Players” (2610.33845).

AutoTavern as a reality-anchored research process

AutoTavern models research as an evolving collection of artifacts: the simulator, opponent models, evaluation exams, policy, research memory, and verification gates. The system’s defining design choice is that improvements to the proxy objective are not accepted as evidence of progress unless they survive independent checks and, ultimately, comparison with live-game behavior.

The research agents do not communicate through unconstrained conversational exchange. Instead, they write to typed and versioned stores containing findings, rule decisions, open questions, experiment specifications, handover notes, and persistent lessons. Corrections are appended rather than overwriting previous findings. This creates an auditable lineage of conclusions and makes methodological errors part of the system’s persistent state.

Five gates regulate changes to the shared research state:

  1. Build validation requires code changes to pass the test suite.
  2. Contract validation prevents a model trained on one simulator build from being used with another.
  3. Within-build comparison restricts model comparisons to a common environment and multiple random seeds.
  4. Unseen-seed rechecking prevents delivery based solely on selection-seed performance.
  5. Reality validation requires delivered models to play live games whose records are replayed in the simulator.

The fifth gate is especially important because the simulator and opponent models are themselves learned engineering artifacts rather than given infrastructure. Live games exposed 184 defects across game rules, card data, input encodings, client control, and opponent calibration. This result establishes that live deployment was not merely a final demonstration; it was an active source of environment correction.

The system’s process-level self-improvement is narrower and more concrete than unrestricted self-modification. The agents did not rewrite their own underlying LLM code. Instead, methodological failures were converted into persistent lessons, new gates, or standing rules. For example, a copied-game search appeared to improve first-place rate by 23.6 percentage points because the copied trajectories retained the simulator’s random-number state and therefore leaked future shop and combat outcomes. After reseeding each sample, the apparent improvement became −0.65±1.14-0.65 \pm 1.14 points. Similarly, winner’s-curse effects from selecting the best snapshot on evaluation seeds motivated the unseen-seed delivery gate. The implication is that the principal mechanism of self-improvement is institutional memory plus procedural constraint, not autonomous invention of a new research algorithm.

Figure 1

Figure 1: AutoTavern’s six-agent architecture and its training, research, and live-ladder loops.

TavernGym and the problem of environment fidelity

TavernGym is presented as the first full-content reproduction of the live Battlegrounds game suitable for training and evaluation. It implements all 978 game objects in patch 36.6.3, including minions, heroes, Hero Powers, trinkets, spells, and other cards. Its Rust engine exposes Python bindings, batched environments, exact save-and-restore, a player-view observation interface, and 245 discrete actions with an exact legality mask.

The simulator uses one seeded random generator, making a seed and action sequence exactly reproducible. Recruit and combat phases share an effect context, and card behaviors are represented through event hooks. This architecture is technically consequential because many Battlegrounds mechanics span phases and interact through triggers, attachments, deathrattles, auras, and persistent effects. The engine also uses an arena of serializable entities, facilitating state copying and lookahead.

Performance is high enough to support extensive PPO training and simulated evaluation: a single CPU core runs approximately 190–280 complete eight-player games per second, while late-game combats run at roughly 52,000–76,000 per second. The paper reports 375 rule-verification records and 220 confirmed rule decisions. Fuzzing checks state invariants after every random legal action, and live-game replay identifies discrepancies between the client and the simulator.

Figure 2

Figure 2: TavernGym’s Rust engine, Python interface, derived programs, and shared client encoding.

The paper’s strongest methodological point is that simulator fidelity cannot be established solely through internal tests. The live loop found 35 rule and card-behavior defects, 11 card-data or offer-rule defects, 73 input-encoding discrepancies, 51 client-controller defects, and 14 opponent or exam-calibration problems. Consequently, “faithful reproduction” should be interpreted as the result of repeated alignment against one live patch, not as a formally complete proof of semantic equivalence.

TavernAgent architecture and training

TavernAgent is an 18-million-parameter entity transformer. The observation is tokenized into the player’s minions, hand cards, tavern offers, pending choices, and opponents, with a maximum of 56 entity tokens plus a global token. Card representations combine identity embeddings, static attributes, and an embedding of the card’s rule text. The rule-text component allows rare or newly encountered cards to receive a semantically informed initialization rather than relying only on identity-specific data.

An eight-layer transformer with hidden dimension 384 and eight attention heads feeds three output heads: a pointer head over the 245 masked actions, a value head, and an auxiliary placement head. The policy is trained with PPO using terminal placement utility. Each training stage involves approximately 310 million decisions and 570,000 games, beginning from the preceding stage under a KL anchor. Training progresses from simplified rules to full content, player-view observations, first-place objectives, and increasingly calibrated opponent libraries.

The most important training intervention is opponent calibration. Rather than relying on self-play, the policy faces seven library seats whose boards are sampled from statistics of strong human players and recalibrated to resemble the opponents encountered in live deployment. From the same checkpoint and training budget, calibrated opponents increase main-exam first-place rate from 20.9% to 27.2%, and harder-exam first-place rate from 10.3% to 13.5%. This result supports the paper’s broader argument that opponent-model misspecification is a major source of proxy failure in multiplayer environments.

The delivered sequence of 23 versions improves substantially on the fixed simulator exams. TavernAgent’s average placement improves from 3.40 to 2.33 on the main exam, while first-place rate increases from 1.9% to 41.5% and top-four rate reaches 89.0%. On the harder exam, the final version reaches an average placement of 3.28, a 23.8% first-place rate, and a 73.2% top-four rate.

System or version Main-exam average placement First place Top four
Random legal actions 7.97 0.0% 0.0%
Scripted bot 7.54 0.0% 0.5%
TA-1 3.40 1.9% 83.4%
TA-11 2.83 18.5% 85.5%
TA-23 2.33 41.5% 89.0%

The improvement is not attributable only to model scaling. An early comparison of 3.5M-, 8M-, and 18M-parameter networks shows a consistent but moderate benefit from larger models. The research process, simulator corrections, opponent calibration, curriculum, and deployment feedback account for the dominant longitudinal improvement.

Figure 3

Figure 3: TavernAgent’s entity-token representation, rule-text-enhanced card embeddings, transformer trunk, and three output heads.

Live-ladder performance

TavernAgent was deployed on the live ranked ladder through a controller that converted the client state into the simulator’s representation and executed the policy’s decisions. A human pressed the corresponding shortcut key, but the paper states that the human made no game decisions. The deployment covered one account, one patch, and 392 games across days 5–18.

The rating increased from 6,000 to 14,007 during the logged sequence and reached approximately 15,000 shortly afterward. Across games without client failures, the agent achieved an average placement of 3.22, a 16.4% first-place rate, and a 77.1% top-four rate. The latest versions, TA-19 through TA-23, achieved an average placement of 2.37, 32.6% first places, and 91.3% top-four finishes.

Figure 4

Figure 4: TavernAgent’s live-ladder rating trajectory over 392 games, including version intervals and deployment-induced pauses.

The paper makes a stronger comparison using the public leaderboard’s estimated-placement metric. In the final 20 leaderboard records, TavernAgent averages placement 1.60, with 80% first places and 90% top-four finishes, compared with 2.34, 59%, and 81% for the server’s ten highest-rated players collectively. The paper therefore claims that the system plays at the level of the server’s best players.

This comparison requires qualification. The leaderboard placements are inferred from rating changes rather than directly observed game-by-game outcomes, and the agent’s sample is only 20 records. The rating is also accumulated over a short period and depends on the number of games played. In addition, 96 of 388 games with recorded placements contained client failures and are excluded from the primary placement statistics. These limitations do not invalidate the live result, but they make “rivals top players” a claim about a short, deployment-specific evaluation window rather than a definitive estimate of long-run population strength.

The ladder nevertheless revealed failures not captured by the simulator. TA-10 nearly doubled the exam first-place rate of its predecessor, from 12.8% to 24.2%, yet its rating declined from 8,968 to 7,658 over 32 games. Investigation identified client failures and an early- to mid-game weakness hidden by the exam. The live loop consequently acted as a falsification mechanism for simulated progress.

TavernBench and the build-versus-play distinction

TavernBench evaluates whether general-purpose LLMs can directly perform the decisions made by TavernAgent. It contains 960 tasks across 40 scenarios and eight categories, including economy, combat, positioning, ordering, targeting, selection, and strategy. Labels are generated through TavernGym simulation, repeated combat rollouts, or play-out comparisons. All models receive textual game states and card rule descriptions, while TavernAgent receives its native structured engine state.

On the 368 tasks shared by all systems, TavernAgent achieves 91% accuracy, compared with 63% for the strongest directly prompted LLM, GPT-6 Astra. Claude Opus 5.5 and Claude Sonnet 5.5 reach 52% and 53%, respectively. TavernAgent is near-perfect on combat, positioning, ordering, and targeting, while its lower selection score of 64% and strategy score of 75% indicate that high-level choice among uncertain alternatives remains more difficult even for the specialized policy.

System Play accuracy Real-time accuracy Median time
TavernAgent 91% 90% 0.03 s
GPT-6 Astra 63% 0% 2.4 s
Claude Sonnet 5.5 53% 0% 1.4 s
Claude Opus 5.5 52% 0% 6.2 s
GPT-6.1 Sol 46% 0% 2.0 s
Jev 37% 37% 0.26 s

Latency produces an even sharper separation. TavernAgent answers in a median of 0.03 seconds and retains 90% accuracy under the paper’s one-second decision budget. Every evaluated LLM except DeepSeek-V4.1-Flash falls to 0% real-time accuracy under that threshold; DeepSeek reaches 26%. Since Battlegrounds turns chain many dependent operations, per-decision errors compound rather than average independently. The practical result is therefore not merely that LLMs are slower, but that their latency and error rates are jointly incompatible with the action cadence of live play.

The benchmark also separates rule execution from strategic play. Frontier LLMs perform well on rule tasks—GPT-6 Astra reaches 95%, Claude Opus 92%, and Gemini 3.8 Flash 90%—but perform much worse on play-out decisions. This supports the paper’s explicit claim that reading a card’s rules is not equivalent to selecting the action that maximizes downstream placement.

Providing TavernGym as a tool closes much of the gap. GPT-6 Astra improves from 62% to 97% on the relevant short-term tasks, while other models also improve substantially. The remaining errors arise from illegal or mis-indexed actions, incomplete candidate search, and the combinatorial size of purchase sequences. This ablation suggests that a large component of the direct-LLM deficit is the absence of a fast, exact world model and action evaluator. However, the tools do not establish that an LLM can independently reproduce TavernAgent’s long-horizon policy: the tool calls remain budgeted, task-specific, and evaluated on constrained scenarios.

Figure 5

Figure 5: TavernBench accuracy by capability and the trade-off between play accuracy and per-decision latency.

What the ablations reveal about the learned policy

The paper measures the value of decision classes by randomizing, removing, or hiding one class at a time. Discover choices, Dark Gifts, and targeting decisions cost approximately 1.4–1.9 average placement positions when disrupted; trinket decisions cost about half a placement, and Hero Power decisions approximately one quarter. This result indicates that the policy’s performance is concentrated in a small number of high-leverage branching decisions rather than uniformly distributed across all actions.

The policy also exhibits a distinct hero profile from human players. Across 111 heroes, the correlation between TavernAgent’s hero-specific placement and public human statistics is only r=0.13r = 0.13. The agent performs relatively well with heroes that humans rate as weak, such as Fungalmancer Flurgl, Trade Prince Gallywix, and Guff Runetotem, but underperforms relative to humans with heroes requiring multi-turn planning, including The Jailer, Alexstrasza, and Captain Eudora.

This weak correlation is important because it contradicts a simple interpretation of the agent as a general imitation of top human play. TavernAgent achieves strong aggregate performance while using a policy distribution that differs materially from human hero preferences and strengths. The authors also caution that the absolute comparison is confounded by the agent’s library opponents rather than human opponents, so the correlation measures relative profile similarity, not equivalent head-to-head hero strength.

Figure 6

Figure 6: Hero-specific average placement for TavernAgent compared with public human-player statistics.

Warband-growth analysis provides a related but limited diagnostic. The final agent matches approximately the top 1% of human players in warband strength through turn 9 and exceeds their reported attack-and-health totals by two to eight times from turn 11 onward. Because the curves are survivor curves and TavernAgent is evaluated against library seats rather than actual humans, the result measures growth dynamics rather than direct competitive superiority.

Figure 7

Figure 7: Warband strength across turns for TavernAgent versions and human-player statistics.

Limitations and open questions

The evaluation is concentrated on one game patch, one account, one deployment configuration, and a short live-ladder interval. Hearthstone Battlegrounds is continuously updated, so the simulator’s 978-object fidelity is patch-specific. The paper does not establish how rapidly AutoTavern can reconstruct a substantially changed ruleset or how much of its research memory transfers across patches.

The live comparison also has statistical and measurement limitations. The top-player comparison uses 20 leaderboard records and placements inferred from rating changes. Client failures affect 96 games, and the deployment still includes a human pressing keys, even though the paper reports that the human made no decisions. The calibrated opponent libraries are designed to resemble encountered opponents but remain proxies; consequently, high exam performance cannot by itself establish population-level human strength.

TavernBench is simulator-labelled and partly uses earlier TavernAgent versions as evaluators, particularly for strategic play-out tasks. This creates a potential dependence between the benchmark and the system being evaluated. The authors mitigate this through multiple labeling procedures and public human statistics for some tasks, but independent human-expert evaluation of the full benchmark would strengthen the claim that the benchmark measures game quality rather than agreement with the simulator or an earlier policy.

Finally, the study does not isolate the marginal contribution of LLM research agents from that of conventional engineering and reinforcement learning. AutoTavern uses PPO, a transformer policy, extensive compute, hand-defined interfaces, and human adjudication. The experiments demonstrate that LLM agents can organize and execute this pipeline under the specified framework; they do not show that LLMs independently discovered the complete algorithmic design or that the same process would outperform a comparably resourced human engineering team.

Open questions include whether reality-anchored memory and verification gates remain effective under rapid patch changes, whether independent evaluation environments can replace policy-generated labels, and whether the build-versus-play gap persists when LLMs receive persistent tool access, structured state, and recurrent planning over full turns rather than isolated benchmark tasks.

Conclusion

AutoTavern demonstrates a technically substantive form of LLM-mediated research automation. Its contribution is not a new RL algorithm but an integrated process for constructing, validating, correcting, and deploying a specialized game-playing system under imperfect simulation. The combination of typed research memory, verification gates, opponent calibration, and live-game replay enabled TavernGym and TavernAgent to progress from an initial 1.9% simulated first-place rate to 41.5%, while the deployed agent reached approximately 15,000 ladder rating and reported short-window results superior to the server’s ten highest-rated players.

The central empirical distinction is between constructing a capable policy and executing its decisions through language. TavernAgent reaches 91% on TavernBench play tasks at 0.03 seconds per decision, whereas the best directly prompted LLM reaches 63% and fails the one-second live-play constraint. The paper therefore supports a precise conclusion: under this setting, LLM agents are more effective as components of a tool-using research and engineering process than as direct controllers of a high-dimensional, real-time, stochastic game.

Whiteboard

Explain it Like I'm 14

1. What is this paper about?

This paper describes AutoTavern, a system that uses several AI “research assistants” to build an AI player for Hearthstone Battlegrounds.

In this game, eight players collect and arrange fantasy creatures. The creatures then fight automatically. Players must make many decisions, such as:

  • Which creatures to buy or sell
  • How to arrange their team
  • When to upgrade the tavern
  • Which special powers or cards to use
  • How to prepare for unknown opponents

The researchers wanted to know whether AI agents powered by LLMs, could do more than answer questions or write code. Could they actually build a complete game-playing system that performs as well as top human players?

Their answer was largely yes.

2. What questions did the researchers ask?

The main research question was:

Can a group of LLM-based agents build a strong AI system for a difficult, changing, real-world game?

The researchers also explored several smaller questions:

  1. Can AI agents build an accurate computer version of the game?
  2. Can they train another AI to make good decisions in that game?
  3. Can the trained AI play the real online game?
  4. Can the system improve itself by learning from mistakes?
  5. Are LLMs better at building a game-playing AI than at playing the game directly?

The last question was especially important. The researchers compared ordinary LLMs, such as chatbot-style models, with the specialized AI that the LLM agents created.

3. How did they do the research?

Building a team of AI researchers

AutoTavern used several specialized AI agents. Each agent had a different job, much like members of a human research team:

  • An environment agent built the game simulator.
  • A training agent trained the game-playing AI.
  • An opponent agent created computer opponents that behaved like human players.
  • An evaluation agent tested whether changes actually helped.
  • A deployment agent connected the AI to the real game.
  • A research leader decided what problem to work on next.

The agents shared a carefully organized research memory. This memory stored experiments, discoveries, mistakes, corrections, and rules about the game.

Creating TavernGym

The agents built TavernGym, a computer simulation of Hearthstone Battlegrounds. A simulator is like a practice version of a game where a computer can play thousands of matches quickly.

TavernGym included:

  • All 978 game objects in the selected game version
  • The buying phase and the automatic battle phase
  • Heroes, minions, spells, trinkets, and special effects
  • Hidden information, such as what opponents might be planning
  • The same legal actions available in the real game

The simulator could run about 190 to 280 complete eight-player games per second on one computer processor. This allowed the AI to practice far more quickly than a person could.

Training TavernAgent

The researchers then trained TavernAgent, the game-playing AI.

They used a method called reinforcement learning. In everyday terms, this is like training a player by letting it try many actions, seeing how well it finishes, and rewarding actions that lead to better results.

The AI received a reward based mainly on its final position:

  • 1st place was best.
  • 8th place was worst.

The researchers used PPO, a reinforcement-learning method that helps an AI improve without changing its behavior too wildly after each training session.

The AI played against computer-controlled opponents based on statistics from strong human players. These opponents were repeatedly adjusted using information from real games.

Testing and checking the system

AutoTavern used several safety checks, called verification gates. These were designed to stop the agents from believing results that were caused by bugs or luck.

For example:

  • Code had to pass tests before being used.
  • A model had to be matched with the exact simulator version it was trained on.
  • New versions had to be tested with different random starting conditions.
  • A model had to be tested on situations it had not been selected on.
  • Successful models had to play real online games.

This is similar to testing a science experiment several times instead of trusting one lucky result.

Learning from real games

The AI played real games on the live ladder. The researchers compared what happened in the real game with what the simulator predicted.

When the two did not match, the agents investigated the problem. During the project, they made 184 fixes to game rules, card information, input formats, computer opponents, and the controller connecting the AI to the game.

4. What did they find?

The AI became a very strong player

Over 20 days, the system created 23 versions of TavernAgent.

In simulated games, its first-place rate improved from 1.9% for the first version to 41.5% for the final version. Its average finishing position also improved from 3.40 to 2.33.

When playing the real online ladder, the AI’s rating rose from about 6,000 to about 15,000. The researchers reported that its recent results were better than those of the server’s ten highest-rated human players on several measures.

For its last 20 reported games:

Measure TavernAgent Top 10 human players
Average placement 1.60 2.34
First-place rate 80% 59%

These results suggest that the specialized AI was capable of playing at, or even above, the level of top players during the tested period.

The specialized AI was much better than general LLMs at playing

The researchers created TavernBench, a test containing 960 game-related tasks across 40 situations.

TavernAgent answered 91% of the play tasks correctly. The best general-purpose LLM tested scored 63%, while other models scored between 22% and 53%.

The specialized AI was also much faster:

  • TavernAgent: about 0.03 seconds per decision
  • General LLMs: about 1.4 to 26 seconds per decision

This speed matters because a real game turn does not allow unlimited thinking time.

LLMs understood rules but struggled to choose the best move

The general LLMs were often good at answering questions such as:

“What does this card do?”

However, they were much worse at questions such as:

“Which action should you take now to give yourself the best chance of winning?”

This is an important difference. Knowing the rules of chess is not the same as knowing the best chess move. Similarly, knowing what every card does is not enough to manage a complete Battlegrounds game.

Using a simulator helped LLMs

When general LLMs were given access to TavernGym as a tool, their performance on some combat questions improved greatly. This suggests that computers are often better than LLMs at performing complicated calculations and testing many possible outcomes.

The agents discovered important mistakes

The self-checking process found several problems that would have made the results misleading.

For example:

  • A copied game accidentally kept information about future random events. This allowed the AI to “see the future.”
  • Choosing the best result from many experiments made improvements look larger than they really were.
  • The simulator and the real game sometimes described the same situation differently.
  • Some computer opponents did not behave enough like the opponents the AI met online.
  • A version that looked better in simulation actually performed worse on the real ladder.

These discoveries show why testing only inside a simulator can be dangerous. A simulator may contain hidden mistakes, just as a flight-training program would be unsafe if its controls did not match those of a real airplane.

5. Why are these findings important?

The paper’s main message is:

LLM agents can be much better at building a specialized AI system than at directly doing the task themselves.

A general LLM may be slow and make mistakes when asked to play every turn. But it can still help create:

  • A realistic simulator
  • Training programs
  • Testing systems
  • Opponent models
  • Error-checking procedures
  • A fast specialized game-playing AI

The research also shows the value of a reality loop. This means repeatedly comparing the computer’s predictions with what happens in the real world. When the results disagree, the system fixes itself and updates its methods.

The approach could be useful beyond games. Similar systems might help build AI for:

  • Robotics
  • Traffic planning
  • Business simulations
  • Scientific experiments
  • Software engineering
  • Complex decision-making tasks

However, the results should not be treated as proof that AI can solve every problem automatically. The study tested one game, one game version, and one period of online play. Human researchers still set goals, resolved unclear rules, and helped with deployment. The system also depended on a carefully built simulator and many computer experiments.

Conclusion

AutoTavern used a group of LLM-based research agents to build a realistic Hearthstone Battlegrounds simulator and a specialized AI player. The agents performed thousands of experiments, found and corrected many mistakes, and improved the AI by testing it in both simulation and real games.

The resulting TavernAgent played very strongly and was faster and more accurate than general-purpose LLMs when making game decisions.

The most important lesson is that an AI LLM does not have to be the best player itself to build a very good player. In this study, LLMs were better at organizing research, writing software, testing ideas, and improving a specialized system than at directly playing the entire game.

Practical Applications

Immediate Applications

The paper’s artifacts and engineering practices can support the following uses now, provided licensing, game-provider rules, and reproducibility are addressed.

  • Game-AI research and benchmarking — Academia / software
    • Use TavernGym as a reproducible environment for reinforcement learning, partial-observability, multi-agent planning, opponent modelling, and stochastic decision-making.
    • Use TavernBench to evaluate models on action selection, combat reasoning, strategy, latency, and simulator-verified outcomes rather than text-only explanations.
    • Build course assignments and research baselines around PPO, entity transformers, legal-action masking, seeded evaluation, and game replay.
    • Dependencies: The released code and game data must be legally redistributable and maintained across patches. Results may not transfer directly to other games because the study targets one patch and one title.
  • Decision-support tools for human players — Consumer software / gaming
    • Develop an advisory assistant that displays recommended purchases, positioning, combat targets, upgrade timing, and Hero Power use during a turn.
    • Use TavernGym for fast “what-if” analysis, such as comparing alternative purchases or positioning choices through thousands of simulated combats.
    • A safer product form would be a post-game analyst or opt-in training coach rather than an autonomous ladder player.
    • Dependencies: The tool must comply with the game publisher’s terms of service, plugin rules, anti-cheating policies, and limits on automation. Simulator fidelity must be revalidated after every content update.
  • Automated game testing and regression detection — Game development / quality assurance
    • Apply the engine’s seeded randomness, invariant checking, fuzzing, exact save/restore, and replay comparison to test new cards, interactions, combat rules, and client updates.
    • A workflow could generate legal action sequences, replay them across engine versions, and flag changes in state transitions, damage, offers, or card effects.
    • The reality loop can be adapted to compare telemetry from production games with predictions from a test simulator.
    • Dependencies: Access to authoritative game data and sufficiently detailed telemetry is required. Automated tests cannot resolve mechanics that are ambiguous or hidden from available logs.
  • Research-agent orchestration for software engineering — Software / enterprise R&D
    • Replicate AutoTavern’s division of labor with specialized agents for environment construction, training, evaluation, deployment, and monitoring.
    • Use a typed, versioned research memory containing findings, corrections, experiment metadata, unresolved questions, and persistent lessons.
    • Apply gates analogous to:
    • build and test validation;
    • model–environment compatibility;
    • same-version comparisons;
    • evaluation on unseen seeds or held-out data;
    • production or field validation.
    • This could support autonomous experimentation in simulation, recommender systems, robotics, or infrastructure optimization.
    • Dependencies: Human oversight remains necessary for ambiguous requirements, safety constraints, resource allocation, and interpretation of real-world failures. LLM-generated code and conclusions still require independent review.
  • Reproducible machine-learning experimentation — Academia / industrial ML
    • Adopt the paper’s practice of tying each model to an environment or data version through hashes and refusing incompatible checkpoints.
    • Maintain immutable findings and record corrections as new entries rather than overwriting earlier conclusions.
    • Register experiments, seeds, resource budgets, successors, and selection criteria to reduce winner’s curse, leakage, and retrospective cherry-picking.
    • Dependencies: Teams need disciplined experiment tracking and sufficient compute for repeated evaluation. These controls improve reliability but do not eliminate hidden confounding or measurement error.
  • Fast simulation for planning and lookahead — Robotics, logistics, and operations research
    • Reuse the engine design principles—cheap serializable states, deterministic seeds, batched simulation, legal-action masks, and exact restoration—for domains such as warehouse scheduling, fleet dispatch, inventory control, and robot task planning.
    • A policy can evaluate candidate actions in a simulator while a separate controller enforces legality and safety.
    • Dependencies: The simulated environment must accurately reflect operational constraints. Real-world validation is essential because optimizing an inaccurate simulator can produce the same proxy-drift failure observed in the paper.
  • Real-time policy inference — Edge AI / interactive systems
    • The contrast between TavernAgent’s approximately 0.03 s decisions and slower general-purpose LLMs supports using compact specialized policies for latency-critical actions.
    • Potential products include game agents, interactive tutoring policies, adaptive interfaces, and control systems where a LLM performs offline research but a smaller policy executes decisions.
    • Dependencies: The action space must be sufficiently structured, legal actions must be known, and the policy must be monitored for distribution shift.
  • Benchmarking tool use in LLMs — Academia / model evaluation
    • Use TavernBench-style tasks to test whether an LLM can use an external simulator or planning tool, distinguishing rule recall from effective sequential decision-making.
    • Evaluate both accuracy and deadline-constrained performance, since a correct answer delivered too late may be unusable.
    • Dependencies: Benchmark prompts, labels, and simulator versions must remain hidden or carefully controlled to prevent contamination. Scores are domain-specific and should not be treated as general intelligence measures.
  • Policy and governance guidance for autonomous AI experiments — Public policy / research administration
    • Use the paper as a practical example of why autonomous research systems need provenance, approval gates, audit logs, held-out tests, and deployment feedback.
    • Organizations can require that agent-produced claims be linked to code, data, configuration, evaluation seeds, and evidence of external validation before entering a shared knowledge base.
    • Dependencies: Governance must define who is accountable for agent actions, how incidents are reported, and when human authorization is mandatory.

Long-Term Applications

These applications require further research, broader validation, legal agreements, or substantial engineering beyond the study’s demonstrated scope.

  • General-purpose self-improving research laboratories — Academia / industrial R&D
    • Extend AutoTavern from a game-specific system to domains such as drug discovery, materials science, chip design, energy optimization, and climate modelling.
    • The agents could iteratively improve simulators, candidate solutions, evaluation suites, and research procedures while periodically comparing predictions with laboratory or field measurements.
    • Dependencies: Domain simulators must be sufficiently accurate; experiments may be expensive or slow; safety and regulatory review are required. In high-stakes domains, a game-style autonomous deployment loop is not adequate by itself.
  • Robotics policies trained in simulation and corrected from field data — Robotics
    • Build reality-anchored loops in which simulation-trained policies are tested on robots, discrepancies are replayed in simulation, and updated policies are evaluated before redeployment.
    • Typed memory and verification gates could track hardware configurations, sensor encodings, controller versions, and safety constraints.
    • Dependencies: Sim-to-real transfer, hardware wear, sensor noise, physical safety, and rare failure modes are much more consequential than in a game. Deployment should require sandboxing, human supervision, and formal safety checks.
  • Adaptive industrial control and energy management — Energy / manufacturing
    • Apply fast simulators and calibrated opponent or demand models to optimize battery storage, grid balancing, production scheduling, or building energy use under uncertainty.
    • Real-time telemetry could continuously recalibrate demand models, while unseen scenarios and safety constraints gate policy updates.
    • Dependencies: Reliable sensor data, stable interfaces, cybersecurity, and hard operational constraints are essential. Optimizing average performance must not compromise grid reliability, equipment safety, or service continuity.
  • Autonomous financial decision systems — Finance
    • The framework could inform portfolio execution, market-making simulation, fraud-response planning, or stress testing by combining scenario generation, versioned experiments, and out-of-sample evaluation.
    • Reality-loop validation could compare simulated market behavior with observed execution and adverse events.
    • Dependencies: Markets are non-stationary, adversarial, and strongly affected by an agent’s own actions. Historical or simulated results can be misleading; deployment would require regulatory compliance, risk limits, explainability, and independent model validation.
  • Personalized education and tutoring policies — Education
    • A simulator could model learner states, misconceptions, engagement, and intervention outcomes, allowing an agent to select exercises or explanations under a time and attention budget.
    • The paper’s distinction between knowing rules and making effective sequential decisions suggests evaluating tutors by long-term learning outcomes rather than answer quality alone.
    • Dependencies: Student models are uncertain and ethically sensitive. Real-world trials, privacy safeguards, teacher oversight, and fairness analysis are required; synthetic learners cannot substitute for educational evidence.
  • Clinical decision-support systems — Healthcare
    • A carefully constrained version could simulate treatment pathways, compare possible interventions, and use structured verification gates before recommending actions.
    • The reality-loop principle could support post-deployment monitoring for discrepancies between predicted and observed outcomes.
    • Dependencies: This is a high-risk extension. Clinical validation, prospective trials, medical-device regulation, privacy protection, interpretability, and clinician responsibility are mandatory. The paper does not demonstrate medical validity and provides no basis for autonomous treatment.
  • Continually updated agents for changing environments — Software / online services
    • The patch-overlay model and rule hashes could inspire agents that remain operational as APIs, policies, product catalogs, or business rules change.
    • A deployment controller could reject models trained on incompatible schemas and trigger retraining when live observations diverge from simulation.
    • Dependencies: Continuous updates can introduce silent regressions, feedback loops, or specification drift. Organizations need rollback mechanisms, compatibility testing, staged deployment, and explicit change approval.
  • Autonomous multiplayer or competitive game agents — Gaming / entertainment
    • A fully autonomous Battlegrounds agent could become a commercial coaching product, tournament participant, accessibility tool, or adaptive non-player opponent.
    • The same approach could extend to other games with hidden information, stochastic rewards, and changing content.
    • Dependencies: Publisher authorization, anti-cheat safeguards, fair-play rules, privacy protections, and transparent disclosure are necessary. Performance on one patch and one ladder does not establish robust superiority across patches, player populations, or games.
  • Formalized “research-process learning” systems — AI safety / meta-research
    • The paper’s lessons-to-gates mechanism could evolve into systems that automatically identify recurring methodological errors and add new checks to future experiments.
    • Such systems could maintain a machine-readable audit trail of why a conclusion changed, which assumptions failed, and which tests were added.
    • Dependencies: Automatically generated gates may encode incorrect assumptions or become overly conservative. Human auditors must review process changes, especially when the system is allowed to influence its own evaluation criteria.
  • Standardized reality-anchored evaluation infrastructure — Cross-sector policy and academia
    • A future platform could provide reusable components for deterministic simulators, live-data replay, held-out evaluation, model–environment contracts, latency measurement, and deployment monitoring.
    • This would help compare autonomous agents in robotics, finance, healthcare, and industrial control using both simulated and real-world evidence.
    • Dependencies: Cross-domain standards for data access, safety, reproducibility, privacy, and responsible deployment must be established. Directly transferring the paper’s metrics or gates across sectors would require domain-specific adaptation.

Glossary

  • Auto-battler: A multiplayer strategy game in which players build teams that fight automatically. “Blizzard's eight-player auto-battler”
  • Auxiliary head: An additional neural-network output used to predict a related task during training. “a value head and an auxiliary placement head share the trunk”
  • Calibration: Adjustment of a model or simulated opponents so that their behavior matches real-world observations. “recalibrated, turn by turn, to the opponents the agent actually met in live games”
  • Checkpoint: A saved state of a model, typically including its learned parameters, that can be used for evaluation or further training. “from the same checkpoint and with the same budget”
  • Closed loop: A system in which outputs or observations from deployment are fed back into later development and decision-making. “in a closed loop of training, research and live games”
  • Contract gate: A verification condition ensuring that a model is used only with the environment or simulator version for which it was trained. “G2~contract: every model is tied to the simulator build it was trained on”
  • Curriculum: An ordered training strategy that presents increasingly complex tasks or environments to a learning system. “A training agent designs recipes and curricula”
  • Embeddings: Learned vector representations that encode the properties or meaning of inputs for a neural network. “a card is represented by an identity embedding”
  • Entity transformer: A transformer architecture that represents individual game entities as tokens and processes their relationships. “TavernAgent is an entity transformer”
  • Evaluation gate: A procedural or computational checkpoint that a candidate system must pass before being accepted. “each passing an evaluation gate”
  • Fuzzing: Automated testing that generates many varied or random inputs to expose implementation errors and invariant violations. “unit tests, fuzzing with invariant checks after every action”
  • Game horizon: The number of sequential decisions or time steps over which an agent acts before an outcome is determined. “a horizon of hundreds of decisions with a reward only at the end”
  • Hidden information: Information relevant to the game that is not observable by the agent. “hidden information about seven opponents”
  • Input encoding: The representation or formatting used to convert an environment state into a model’s input. “fixes of rules, input encodings and opponent models”
  • Invariant: A property that should remain true throughout execution, regardless of the actions taken. “fuzzing plays random legal actions and checks state invariants after every action”
  • KL anchor: A regularization mechanism that constrains a new policy from diverging too far from an earlier policy using Kullback–Leibler divergence. “starts from the previous stage under a KL anchor”
  • Legal-action mask: A representation that identifies which actions are valid in a given state and prevents invalid actions from being selected. “The RL interface exposes 245 discrete actions with an exact legal mask”
  • Lookahead: Planning that evaluates the consequences of possible actions by simulating future states. “one-step lookahead”
  • Monte Carlo tree search: A search algorithm that explores possible future actions through repeated simulations and tree expansion. “built a Monte Carlo tree search assistant”
  • Opponent model: A computational representation of how other players or agents behave. “an opponent agent builds human-like opponents from human statistics and live games”
  • Partially observable stochastic game: A multi-agent sequential decision problem with random transitions and incomplete observation of the full state. “We model a game as a partially observable stochastic game”
  • Policy: A function or model that maps observed states to actions or action probabilities. “the policy decides every operation”
  • Policy gradient: A reinforcement-learning approach that directly optimizes the parameters of a policy according to expected returns. “It is trained with PPO”
  • Pointer head: A neural-network output module that assigns scores to selectable items or actions, often by pointing to elements in an input sequence. “a pointer head produces the 245 masked action logits”
  • Proxy drift: The divergence between improvements on a surrogate evaluation objective and improvements in real-world performance. “Proxy drift: J^\hat J improves while JJ does not”
  • Proximal Policy Optimization (PPO): A reinforcement-learning algorithm that updates a policy while restricting excessively large changes between successive policies. “We use a standard learner, PPO”
  • Reality loop: An iterative process that compares simulated behavior with real-world behavior and uses discrepancies to improve the simulator or agent. “AutoTavern answers the first with a reality loop”
  • Reinforcement learning: Machine learning in which an agent learns actions through interaction with an environment and feedback from rewards. “The RL interface exposes 245 discrete actions”
  • Reward shaping: Modification or structuring of learning rewards to encourage useful intermediate behavior. “with a terminal placement utility”
  • Self-play: A training method in which an agent learns by competing against copies or versions of itself. “Rather than self-play, the learner faces seven library seats”
  • Selection bias: Systematic distortion caused by selecting observations or results in a non-representative way. “a reading that reflects noise, a leak or selection is recorded as a result”
  • Stochastic: Involving randomness or probabilistic variation. “The game combines stochastic shops and battles”
  • Surrogate objective: An approximate objective optimized in place of a difficult or expensive real-world objective. “Inside the loop the agents can only improve a proxy”
  • Terminal utility: A reward assigned at the end of an episode or complete sequence of actions. “with a terminal placement utility”
  • Transformer: A neural-network architecture that uses attention mechanisms to process relationships among input elements. “with a transformer”
  • Typed research memory: A shared information store in which entries conform to predefined data types or schemas. “Agents never talk directly; they read and write versioned, typed stores”
  • Unseen seeds: Random-number-generator initializations withheld from model selection and used for evaluation on new stochastic realizations. “re-check on seeds it was not selected on”
  • Value head: A neural-network output that estimates the expected future reward or value of a state. “a pointer head scores the 245 masked actions; a value head and an auxiliary placement head share the trunk”
  • Winner’s curse: The tendency for the best result selected from many trials to overestimate its true performance. “Winner's curse. The best of many snapshots overstated its gain”
  • Zero-shot: Performance on a task without task-specific training or adaptation. “the system the LLM agents built is the strongest player”

Open Problems

We found no open problems mentioned in this paper.

Tweets

Sign up for free to view the 11 tweets with 1617 likes about this paper.