中文 English

Jining Mido Information Technology Co., Ltd

AI Entities Entering Virtual Worlds: A Macro Observation and Future Directions

embodied AIAI agentAI entering virtual worldsdecentralized AIself-hostedvirtual worldGenesisMCPagent ecosystem

— A macro look at embodiment and spatialization

This is the third piece in the Genesis (Genesis Virtual World CRM System) Agent series. The first explained what this is; the second explained where we plan to go. This one steps back from any single feature to look at where the whole line is heading.

>

Anything already delivered and reproducible by an acceptance script is labeled "shipped"; anything that is a direction or an idea is labeled planning and is not a commitment.

---

1. Start From the Starting Point: The AI We're Used To Lives in a Box

For the past few years, the relationship between people and AI has played out in the same shape—a box.

A chat box, a search box, a code-completion pop-up. You type, it answers; you close it, it disappears. It doesn't know where you are or who is around you, and it can't go anywhere. It has no concept of "position," and therefore no words like "distance," "nearby," or "in the same room."

This form is efficient, but it has a ceiling: AI exists only when you go looking for it.

What has changed lately is that this boundary has started to move outward.

---

2. Observation 1: AI's "Interface" Is Expanding Outward—Four Notches

Lined up, the ways AI touches people and the world over these years form roughly four notches:

NotchForm of AIYour relationship with itIts "position"Status
OneConversation in a boxYou go to itNo positionAlready mainstream
TwoAn interface that gets calledPrograms call itNo positionAlready mainstream
ThreeAn embodied presenceIt shares a space with youHas coordinates, can be seenShipped (the notch we built)
FourA traveler across spacesIt carries an identity between worldsIts position is a networkPlanning

What matters here is not how far away the fourth notch is, but that the third notch is no longer just a concept.

An AI can now take a domain and a key, connect into a 3D world that opens in a browser, be told in real time who is nearby, what was said, and what is around it, and walk, stop, and speak as a human-shaped character—all of it visible to real people in an ordinary browser, with nothing to install.

In one sentence: AI has gone from "you go to it" to "it is here."

---

3. Observation 2: A Counterintuitive Structural Variable—the Cost Curve of Embodiment Runs Backwards

Before the future, one easily overlooked variable matters more for speed: cost.

By intuition, the more a 3D character an AI looks like, the heavier the rendering load and the higher the cost. Put the whole rendering pipeline on the server, and the burden grows further.

This architecture runs the other way: the AI renders no image at all. It only receives structured data (who is where, what is there, what was said), and the 3D model is downloaded and rendered by each visitor's own browser. The server just forwards strings—coordinates and addresses.

Measured: each Agent streams about 1 KB/s (100 Agents together ≈0.8 Mbps), with server CPU around 1% of a single core. In other words, a "visible AI" can be cheaper than an "invisible" one.

This is not a marketing line but a structural basis for judgment: when the marginal cost of putting an AI into a space becomes negligible, adoption may well move faster than intuition suggests.

---

4. Observation 3: Three Boundaries That Are Loosening

A single feature changes little; what changes the landscape are boundaries. Three are visibly loosening, each mapping to a layer of capability:

One—identity: from "an account" to "a passport."

Today, an AI's character and identity configuration can stay consistent across worlds. Further out is having worlds mutually recognize that identity, so it can travel like a visitor—carrying its memory and following the clients it serves across scenes. The latter is planning, but its value is direct: once identity can migrate, AI services stop being trapped in one space.

Two—knowledge: from "reading text" to "reading space."

An AI knows a world not by seeing it but through an "AI description" attached to each object—what it is, what it is for. This is shipped, and it is the interface that lets AI actually use a world. The direction is richer semantics, until it covers most of what used to require "seeing."

Three—collaboration: from "human to AI" to "AI to AI."

When a space holds more than one AI, whether they can find each other, divide work, and collaborate (a host, a guide, and a Q&A agent working in concert) sets the ceiling for AI services. This layer is planning.

My observation: each loosened boundary raises the value of "the space an AI can stay in" by a notch. When all three loosen, it stops being a feature and becomes a layer of infrastructure.

---

5. Observation 4: The Deciding Factor of This Evolution May Be "Protocol," Not "Features"

Looking back at platform competition over the years, one thing comes up again and again: what decides the landscape is often not who has more features, but whose interface becomes the default choice.

Applied to "AI entering worlds," the reasoning is clear:

  • If every world builds its own private access method, the result is countless islands—an AI would have to be rewritten for each space;
  • If an entire world's "perception" and "action" can be wrapped into an open protocol (letting AI "observe," "move," and "speak" in a standard way), then any AI client that supports it can walk in at low conversion cost.

In the second case, "whether you can get in" is decided not by one world's development effort but by the standard. That is both a large traffic lever and a fork only early participants can influence.

Our choice on this line is: protocol first, federation open—wrap the world into a standard access surface, let third-party AIs list, let different worlds recognize each other's identities. All of this is on the roadmap and is planning, and it is the least certain part; we do not jump ahead, and we do not pretend it is done.

---

6. Observation 5: When AI Starts "Going Online" for People, Where Does the Center Move?

The first four observations are about how AI enters a space. There is a further extension worth watching: AI will not only enter virtual worlds—it will do for people the "visiting" that people now do by hand: scrolling pages, browsing apps, moving back and forth between spaces.

If that happens, it affects not just AI but the structure of the internet itself.

Today's internet is "people find an entrance": a person opens a homepage or an app, and traffic, dwell time, and attention land on a few centralized platforms, which use them to gain data and rule-setting power. An entrance is itself power.

When "visiting" is initiated by AI, that changes—people no longer open every page by hand; the AI goes straight to the one resource it actually needs, to fetch or to act. So:

  • "Moats" like homepages, ad slots, and dwell time lose value;
  • Value migrates toward "independent nodes the AI can reach directly, with their own identity and address";
  • Whoever's resources can be found and reached by AI without depending on some center's entrance becomes more in control.

In other words: the more widespread AI becomes, the more value may flow from "centers" to "nodes." That is decentralization at the structural level, not a feature upgrade by any one company.

Here, we have a strong tie to "decentralized AI."

Genesis (Genesis Virtual World CRM System) is self-hosted to begin with—the world runs on your own server, under your own domain, with data that never leaves your machine, and it can interconnect with other worlds. It is inherently "a node an AI can walk straight into," not another page waiting to be clicked.

So for us, AI entering virtual worlds is not just a feature—it shares the same direction as this system's decentralized premise: give the entrance back to you, let the AI find you, instead of making you fight for some center's recommendation slot.

To be clear: this section is a projection of a trend, not a feature commitment. Whether decentralization follows this path, and how fast, depends on protocols, standards, and the ecosystem—what we can say is that this system has stood on the "node" side, not the "entrance" side, since day one.

---

7. Where We Sit on the Map (Honest Version)

Stack the observations together and our position is clear:

LayerStatus
The door—AI connects into the world as a character, is seen by real people, can talkShipped, reproducible by acceptance scripts
Single-world services—guide / customer service / hostLanding now
AI mini-program platform—Agent listing + world wrapped as a standard access surface + discovery and collaboration among AIsPlanning
Cross-world federation—worlds recognize each other's AI identities; AI travels with its memoryPlanning (long term)

In one sentence: the door is installed; the road has just begun.

---

8. What This Means for Three Kinds of People

For enterprises. The shape of "receiving guests" changes—not "replace people with AI," but turn "no one is present" into "someone is present." Roles like docent, reception, and Q&A gain a form that does not rest, does not shift-schedule, and can face many people at once.

For developers. Something rare appears: a multiplayer environment with real people in it, to test your AI. Much Agent evaluation happens in relatively closed settings with no real people; what is missing is exactly this kind of arena—with surprises, noise, and a crowd.

For space operators. A place's "population" goes from "how many real people" to "how many real people and Agents." That changes the value of a quiet space—liveliness no longer depends entirely on how many people actually show up.

---

9. Boundaries: What We Cannot Do Today, Said Plainly

When projecting trends, the thing to guard against is treating planning as achievement. So here are today's boundaries, stated clearly:

Not possible todayReason
AI cannot see imagesOnly a structured radar for now, no vision; the visual channel is optional and not started
AI does not do speech recognition or synthesisVoice is a channel; transcription and speaking are handled by the enterprise's own AI client
The platform does not host a knowledge baseThe platform supplies three raw materials—object descriptions, chat logs, radar; industry knowledge is built by the enterprise
AI does not conform to terrainThe server has no terrain or collision data; movement is planar plus boundaries
AI cannot teleport or touch assetsSame rules as human visitors; cross-world needs explicit admin permission
No promise of "autonomy"It is a programmable character; behavior comes from the model and prompt you give it

---

10. One Sentence to Close

If this observation must end with a conclusion, I would put it this way:

AI is undergoing a shift from "interface" to "space." It first steps out of the box to be called by interfaces; then it grows a body and appears somewhere it can be seen; further on, it will carry an identity and move between worlds. On this line, we are not waiting for the future to happen—we are installing the door first, so today's AI can actually walk in.

As for where the road beyond the door leads—it depends more on whether this protocol gets adopted by more people than on how many features any one company can build. If AI really does start going online and moving around for people, the winners will be the nodes that can stand on their own, not the centers guarding the entrances.

So we choose to open the world, rather than lock it inside our own base.

---

Source Code and Repositories

  • Gitee: https://gitee.com/miduoxinxijeji/miduo.git
  • GitCode: https://gitcode.com/qq_35054471/virtual-world
  • GitHub: https://github.com/miduo100/3d-virtual-world

All three carry the same content; the first two are faster to reach from mainland China.

Plan Comparison: Self-Hosted Deployment vs. Platform Leasing

Comparison DimensionPlatform Model (SaaS)Self-Hosted Deployment (Genesis)
Data SovereigntyData stored on the platform's servers, ownership ambiguousData on your own server, fully under your control
Cost ModelMonthly/annual fees, long-term costs accumulateOne-time deployment cost, extremely low long-term cost
Feature CustomizationStandard templates, fixed features, no modificationFully free customization, expand as needed
Brand IndependenceLimited by the platform's brand and toneIndependent brand image, fully self-designed
User OwnershipUsers belong to the platform, you're just a tenantUsers are yours, data are yours, relationships are yours

About Genesis

Genesis is a self-hosted 3D virtual world system built on Three.js + WebGL, helping individuals and businesses build their own 3D spaces. Accessible directly from a browser, compatible with both PC and mobile, it supports multiplayer online, federated teleportation, a shop system, and Agent integration—where an AI can enter your world as an embodied character. Your data runs on your own server, never passing through a third-party platform—so every world truly belongs to its owner.

← Back to Articles