Closing the Loop: Your Coding Agent Can Now Test XR in Real Rooms, No Device Needed

Coding agents like Claude Code, Codex and Devin are now standard kit inside engineering teams, and the conversation has moved on. It is no longer about how to adopt them, it is about how to manage what they produce. Agents write a lot of code, and when your engineers are each running two or three at once you end up asking the obvious question: how do we validate and test all of this while keeping up with the output?

It is a fair question, and the answer depends on what your agent is building and which tools it has to hand. From there you adapt your process. We have been working on the tools side of that for our own users.

Validation came first

As you may have seen, we recently added validation tools to the ViroReact MCP Server. They sit on top of our knowledge base and let an agent check that it interpreted what it read correctly, and that the code it has written is not going to fall over at runtime. The MCP server hands back structured feedback, and when something in the AR or VR code is wrong the agent gets enough detail to pick it up and action it without coming back to you.

But in AR and MR in particular, knowing that your code renders is not enough. The point of the work is seeing your creation run in the real world. That is the part of the loop we have been closing.

Then rendering in the cloud

The next step was letting agents test their work by rendering it remotely in our cloud. By running the ViroReact renderer server side we can validate that your code renders and runs correctly, return a screenshot so you can see it has worked, and send full diagnostics when it has not. That gave your agent the full pass: take the requirement, build it, validate its own work, then test it.

Good, but we were not satisfied. A cloud render tells you the scene works. It does not tell you what the scene feels like in the room it was built for.

Environment testing, live this week

That is why we have released Environment testing.

Record a room, an environment, using the StudioGo app. It is stored on the ReactVision Platform against your team and it stays there, ready to be used again.

From then on you just ask your coding agent to render your scene inside it: "please render my AR scene in my warehouse environment". That triggers a tool on the ViroReact MCP Server, which takes the code straight from your IDE, compiles it remotely on the ReactVision Platform, and renders the scene inside your recording. You and your agent get a far better read on what the code will actually look and feel like once it is in front of a user.

You can keep as many environments as you like. Test the same scene across several different rooms, or, if you are building for one specific space, build and test against that space without needing to be in it. As always, all diagnostics and issues are reported back to your agent, so anything that goes wrong can be actioned right away.

What this changes

Before, your agent could build, validate and test your AR and VR apps with the MCP server. Now it can do all of that against real environments, with no device in your hand and without standing in the room.

Environment testing is now live on the ViroReact MCP Server for all users on a Basic plan or higher. Validation and basic testing remain available to everyone for free.