Xbox Labs: Microsoft Just Blessed the Modders It Used to Ignore
Okay, so here is a sentence I did not expect to type this year. Xbox looked at the wildest corner of the modding scene, the people decompiling games, porting them to hardware they were never built for, and mashing one game's code into another, and said: good work, we want in. On October 13, Xbox CEO Asha Sharma announced Xbox Labs, a new team to explore exactly that kind of thing. Our videos skipped it for time. It deserves a closer look, because the announcement is careful, strange, and possibly more important than it looks.
Start with what we actually know, because the memo is short and it leaves a lot unsaid. Sharma described Xbox Labs as a small group of game makers, engineers, and scientists whose job is to turn emerging ideas into things players and developers can experience. Xbox CTO Scott Van Vliet will lead it. The team will build in the open, share the tools it builds with developers across the industry, and measure success by whether more people are playing and creating. There is already a public site at labs.xbox.com, under the tagline "Let's play with what's next," with an email signup. There are no projects, no tools, and no dates yet. That is the whole announcement: a team, a mission, and a mailing list.
What prompted it: a month of modding chaos
The memo spends most of its space on what inspired it, and that part is specific. In recent weeks, Sharma wrote, games have been rapidly decompiled and rebuilt to run on hardware they were never originally designed to support. Windows PC builds have been translated to run on Apple Silicon. Games have been ported to run inside a browser through WebAssembly and WebGPU, the latter now approaching 90 percent global browser support. And, in her words, some of the biggest games in the world have been remixed into the source code of another.
Those are not hypotheticals. Reporting around the announcement names the examples: a browser port of Halo: Combat Evolved, Call of Duty: Black Ops and Minecraft decompiled to run on the web, and viral clips of Minecraft's Steve battling an Elden Ring boss, built by fusing one game's code into another. These are the kinds of projects that used to live in a gray zone, tolerated at best, and they were suddenly moving fast enough that the head of Xbox wrote a memo about them.
Sharma's verdict on all of it is the most striking line in the memo. She called these experiments unmistakably good outcomes for players, even when, and sometimes because, they challenge our existing business models. Read that again. A platform holder just said, in writing, that fan projects which break its business assumptions are good. That is not the usual corporate line. The usual corporate line is a takedown notice.
The memo that never says AI
Here is the weird part. The memo never uses the word AI. Not once. And yet the whole thing is about AI, and everybody covering it knows it. The tell is the paragraph about agents. Coding became the first major workload for agents, Sharma wrote, because agents can write, run, and test software. Games share many of those same properties. People spend more than 72 billion hours a year playing Xbox games, she added, roughly five times the estimated time spent writing code worldwide.
That is the argument in full: AI agents got good at coding because code can be written, executed, and tested in a loop. Games are the same kind of loop, only bigger, and Xbox sits on an enormous pile of playtime to learn from. The 72 billion hour figure is Microsoft's own estimate, and no outside audit backs it, so treat it as a directional claim rather than a measured fact. But the logic is clear, and it explains why the team is led by Van Vliet, who came to the CTO role in May after running Azure OpenAI and AI infrastructure at Microsoft.
So why not just say AI? Honestly, the likeliest answer is that the word is radioactive inside gaming right now. A GDC survey cited in coverage of the announcement found 36 percent of developers now use generative AI, while 52 percent view it negatively. Sharma herself, in her first memo as CEO back in February, said games would be crafted by humans and created with innovative technology, and pledged not to flood the ecosystem with soulless AI slop. In May, she pulled Gaming Copilot from mobile and canceled its console launch. Announcing an AI lab four days after standing up a new XP division for films and partnerships, in the middle of a restructuring that GeekWire reports included 268 Xbox Game Studios roles cut last month, is a delicate move. The memo threads the needle by talking about agents and experiments and never once saying the word everybody hears anyway.
Why this could actually matter: the preservation angle
Wait, hold on. Strip away the AI framing and there is a much older story here, one that goes back to the very beginning of Xbox. Microsoft already knows how to do this work officially. The Xbox backward compatibility program spent years making old games run on new hardware, legally, with publisher cooperation. What changed is who is doing it now, and how fast. AI-assisted decompilation has collapsed the cost of the hardest part: turning a finished game back into readable, rebuildable code.
The precedent the modding world points to is the Zelda Reverse Engineering Team, which spent 21 months reverse engineering the executable for The Legend of Zelda: Ocarina of Time into human-readable code, work that enabled source ports like Ship of Harkinian. That took almost two years of painstaking human effort. The new wave of projects is doing comparable things in weeks. If Xbox Labs turns that capability into official tools, the implications for preservation are enormous: old games that would otherwise die on dead hardware could get a second life on anything with a browser.

The questions the memo does not answer
For all that, the memo is mostly a vibe, and the hard questions are still wide open. Here are the ones I am watching.
- Where is the IP line? Sharma promises Xbox will be responsible stewards of IP and the communities built around it, but the memo says nothing about where Microsoft draws the line on decompiling games it does not own. Reverse engineering sits in a murky legal area, and a lab that explores it officially will eventually have to state its rules.
- Will Labs ship tools, or just research? A memo is cheap. A decompiler or porting toolkit in creators' hands is the real test, and Sharma's promise to share tools with developers is the commitment to hold her to.
- What happens to the modders? The fan projects that inspired Labs exist in a gray zone today. Does Microsoft's embrace protect them, absorb them, or eventually regulate them? The memo celebrates them, but celebration is not a license.
- Does this change what Xbox builds? The memo insists priorities are unchanged: the 4Cs, great games, hardware. Labs is framed as exploration without abandoning the work already underway. The test is whether Labs output ever shows up in a shipping product, or stays a side project.
- Who benefits first? Players get ports and preservation. Developers get tools. But the economics of a world where any game can be rebuilt for any hardware are genuinely unclear, and publishers who make money on platform exclusivity will have opinions.
Bottom line
I have been watching this industry long enough to know the difference between a pivot and a press release, and right now Xbox Labs could be either. What tips me toward taking it seriously is the specificity of the inspiration. Sharma did not announce a generic innovation lab. She named decompilation, recompilation, browser ports, and remixes, the exact things the community just proved were possible. She put her CTO in charge of it. And she said the quiet part out loud: these experiments are good for players even when they break the business model. That is a real position, and it is one worth holding Xbox to. The next move is theirs, and the whole scene will be watching what Labs actually ships.
Images: Halo screenshots, Xbox Game Studios via Steam.