Agents you can point to.
Start Claude Code or Codex in a project. Speak or type a request with your selection and pointing context. Agents highlight the elements they touch and can narrate their changes.
VOICE + SPATIAL CONTEXT
VR / MIXED REALITY / DESKTOP HOLOGRAPHIC AGENT CONTROL
Your code.
Your agents.
Your world.
Step inside your software. Point at what matters, tell your coding agents what to do, and see their work take shape around you.
Built for Claude Code & Codex · Current developer build
ONE WORKSPACE. THE WHOLE PICTURE.
FROM PROMPT TO SPATIAL CONTEXT
Code structure + Running behavior + Coding agents + Your team
A NEW VIEW OF DEVELOPMENTDon’t just ask for a change.
Don’t just ask for a change.
See where it belongs.
Primitive brings your repositories, runtime traces, and coding agents into a shared 3D space. Explore the architecture, give an agent the context of your selection, then inspect the code it touched. The conversation stays connected to the software.
THE ORIGINAL PRIMITIVE FILMSee software
See software
in a new dimension.
The original landing video shows Primitive’s immersive code visualization and collaboration. Holographic Agent Control builds on that foundation.
THE TOOLSETMore context.
More context.
More control.
A spatial workspace for understanding software
and directing the agents building it.
A codebase you can inhabit.
Navigate a radial map of directories, files, classes, and methods. Watch source edits update the map and inspect changes against Git HEAD at method level.
STRUCTURE + GIT DIFFSBehavior, made visible.
Replay recorded workflows. Follow call stacks, object creation, and captured data mutations. See requests travel between locations and stores fill as a trace advances.
RUNTIME + DATA FLOWYour machines. One landscape.
Explore PC, phone, server, and headset locations as islands. Connect proxies on other machines and direct agents in the project where the work lives.
MACHINES + PROJECTSKeep the output in view.
Bring an agent’s test browser, monitors, windows, or an attached Android phone into VR as screen panels. Use passthrough to work alongside your physical screens.
SCREENS + MIXED REALITYMeet inside the problem.
VR, desktop, and browser viewers share the world, playback position, highlights, and agents. Explore together, or open Blueprint-style graphs to inspect structure and recorded calls.
SHARED SESSIONS + GRAPHSTHE CONTROL LOOP
Point. Speak. Inspect.
You provide direction.
The code stays in the conversation.
Find your context.
Open a project and select the method, directory, or runtime object you want to understand.
Give the agent direction.
“Claude, explain this method.” Your selection goes with the request. Ask for a change when you’re ready.
Inspect what changed.
Follow highlights, review the diff, and inspect a recorded workflow. Answer supported permission prompts in the world.
TRY SAYING
“Explain the changes.”
The agent walks through the diff, pointing at each element.For the moments that need
the whole picture.
Understand an unfamiliar repo
Build a spatial picture of the architecture and ask an agent about the code you’re looking at.
Investigate a workflow
Follow captured execution across calls, objects, and services instead of reconstructing it from separate logs.
Review agent changes together
Bring another developer into the same world and inspect the changed elements with shared context.
BEFORE YOU STEP IN
A few useful details.
Can I use it without a headset?
Yes. The current viewer supports a flat screen and OpenXR VR. A browser viewer can connect to the proxy’s world. Quest 3 has a standalone developer build path with hand tracking and passthrough.
Which languages and runtimes are supported?
The proxy uses tree-sitter for source structure across C#, Python, TypeScript/TSX, JavaScript, Java, Go, Rust, C, C++, Ruby, PHP, Scala, and Bash. Trace detail depends on the capture tool: the Python tracer records data mutations; OpenTelemetry ingestion provides span-level behavior. .NET and Unity tracing tools are also part of the product repositories.
What do I need for agent control?
The proxy runs on your machine and launches installed Claude Code or Codex CLIs using their existing authentication. The optional voice assistant uses a separately configured OpenAI key. The current build requires developer repository access; request access or see the developer guide for prerequisites and setup.
Is this the version on Steam or Viveport?
The holographic agent workspace is the current developer build. The earlier store releases and their controller manual describe the legacy immersive development environment. Request a demo to discuss the current build, or follow the developer setup guide.
Where does my code go?
The proxy analyzes the source on the machine where it runs. Agent requests and optional voice processing use the configured providers. Other viewers access a connected proxy; LAN access uses pairing tokens. Review your provider settings before connecting private code.
A new place
to build what’s next.
Tell us what you’re building. Let’s explore how a spatial agent workspace fits your work.