TabSpace VR 0.5.13
Same tabs. Different Dimension.

Unzip into a permanent folder. Open chrome://extensions, enable Developer mode,
choose Load unpacked, and select the folder containing manifest.json.

Updating: replace the files in your existing extension folder, click Reload in
chrome://extensions, then close and reopen the TabSpace workspace.

Open YouTube or another webpage, click the TabSpace toolbar icon, and choose
Send this tab to VR. Enable Control in VR for voice browsing.

Voice: Start voice uses free Quick commands on this device. If prompted, choose
Download English & start voice. Choose AI assistant for natural conversation
and browser help; sign-in and key connection happen in that same panel. It shows current
availability; trials and checkout are coming soon in unconfigured builds.
When available, separate ten-minute AI/3D trials let you try both features.
Pro unlocks unlimited 3D and AI with your own OpenAI key. API usage is billed
separately by OpenAI.
Connect OpenAI appears when Pro needs a key; remembering it is optional.
Choose Allow page access & start AI voice to start the microphone explicitly.
Quick commands have no cloud speech fallback. Enter VR goes straight to VR.

Voice > Microphone & sound: test the microphone locally, choose an AI input
device and check audio. Preferences are remembered; voice stays off on reload.
Setup check: verify tab/headset readiness or download private diagnostics.
After finishing a file picker in Chrome, choose Tab controls > Resume control.

Ask to play a title from your feed, search YouTube, pause, or resume. Say stop
to cancel a task. Also: open a new tab at youtube.com, go to example.com,
close this tab, make this window bigger, or desktop preview off. New tab
commands need Interactive. The dock retains controls with preview disabled.
See docs/OPENAI.md for privacy and setup.

Immersive VR requires a PC-connected headset and compatible Chrome/OpenXR.
View Only supports viewing and workspace commands, without page control.
Initial setup, sharing existing tabs, and browser permissions still need normal
Chrome input. Explicit new-tab requests can work entirely by voice after setup.
