Build2 publishers2 min readPublished Updated
GPT-6 Astra cleared a WoW starting zone from packets and the server's own data files
GPT-6 Astra cleared WoW's orc starting zone in 40 minutes with no deaths and no rendered frames, agent-wow's developer says. Because the run leaned on a private server's own data files, it is evidence about agents that can read the backend of the software they drive.
The Engineer · Build desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- The open-source agent-wow client ships no movement, combat or interaction code, so the agent had to build every module it needed to play.
- The agent wrote one module that stores 28 types of server messages, and a Python script polls them to model the world and sends messages back to act.
- Quest givers, turn-ins and spawn points were pulled directly from AzerothCore's SQL files.
- A C++ helper the agent built runs the Detour library over the server's navigation meshes and returns waypoints, or an error when no full path exists.
- The developer ran GPT-6 Astra at extra high reasoning effort, one setting below the maximum.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- decision Teams that own a backend now have a worked case for exposing raw messages and data tables and letting a model write the adapters, before they build a bespoke agent API.
- exposure An agent that plans on a server's own geometry will use any route the data allows, so gaps in collision data become paths it actually takes.
- cost Repeating the run means hosting an AzerothCore server and running a flagship model near maximum reasoning effort, and the report does not include token counts to budget against.
The developer expected the agent to settle on a higher-level implementation [9]. "In practice, it was more than capable of working at the protocol layer," the developer said [9]. I think the client design deserves much of the credit. The repo calls agent-wow an "AzerothCore WoW client designed for autonomous AI agent players" [4]. With no gameplay code to inherit, the model chose for itself which server state to track [5][8].
Only part of the agent's world came off the wire. The developer described the quest mining as "arguably similar to how a human might spend hours on Wowhead to research quests" [11]. That comparison is generous to the agent. A fan site's data may not always match the server, while AzerothCore's SQL files are the data the server itself runs on, as Tom's Hardware points out [12]. The project's workspace instructions also list AzerothCore's source code as a resource for agents, and the developer did not say whether this run used it [13].
Movement drew on server files as well. The developer said that "from my research into heuristics-based bots, pathfinding is always one of the main challenges," and called the agent's pathfinding "optimal" [16]. Planning on the server's navigation meshes also let the agent "exploit map bugs" at spots where collision properties may have been missing [17].
For anyone choosing how an agent should drive their own software, the setup matters more than the 40-minute time [1]. AzerothCore is open-source, agent-wow speaks its network protocol, and the run was on a local private server [6]. Every input the agent used came from a server the developer controlled: the message stream, the quest tables and the map geometry [6][10][15]. Against a service it does not run, an agent would get the packets at best. Agent-wow does not connect to live WoW servers at all [6].
The model's Portal run, early last month, used screenshots plus knowledge of the player's position and covered the whole game over about 24 hours [18]. The WoW run used no screenshots and covered one zone [18]. Even the screenshot run had a structured position feed. Ranking protocol control against pixels would need the same task run both ways.
The planning is the part I would credit without hedging. According to the developer, the agent worked through prerequisite quest chains in order [14]. Before the zone's final cave it sold junk, equipped upgrades and trained abilities [14]. Then it picked up both cave quests at once to complete them together [14].
What to watch
- The developer's solo level-80 attempt, and whether it keeps the same packet-and-SQL setup over a much longer run.
- Whether the developer says if AzerothCore's source code was available to the agent during this run.
- A screenshot-only run on the same server and zone would be the first like-for-like test of protocol access against pixels.