Channel control of a 3D world
Channel-to-world runtime control is not ready for general use. A tool appearing in a catalog, a listed device, or a confirmed review does not establish that the installed release can execute that action in a personal world.
Access and permissions
A world name alone may be ambiguous. Any supported operation must identify the intended saved hub and workspace. Account-linked owner approval is separate from dashboard login, channel membership and permission to remember a conversation.
Web and terminal status views do not grant owner authority. Never use a host's account or a different environment as a substitute for an unavailable target. Unsupported or offline operations must remain unavailable.
Understanding status
Queued, saved, verified and displayed are different outcomes. A saved result does not prove that a browser or headset has loaded it. After an uncertain response, inspect the original operation before trying again; do not assume it failed and create duplicate work.
Cancelling a request or changing a selected target cannot recall an action already sent. Existing approvals for deletion, replacement, exports and external operations still apply even where world access has been granted.
Current limits
The hosted browser scene can display supported saved content. That display is not a general-purpose tool executor. Browser account linking or sync does not by itself grant runtime control. Native, Web and terminal controls may report unavailable functionality according to the installed release and platform.
Use currently supported local scene and workspace controls for ordinary work. Do not treat development controls as a supported live channel-to-device workflow.