On your Mac
The backend
Registers your folders, runs the agents, and owns every session. Nothing leaves your machine.
Open beta on TestFlight
Run coding agents from a Vision Pro. Keep the code on your Mac.
AgentRoom drives coding-agent sessions on your own Mac from a Vision Pro. Your code, your logins, and your agents stay where they are.
- macOS 14 or later
- visionOS 26
- Same local network
Three pieces
A backend on your Mac does the work. Two Apple apps talk to it.
On your Mac
The operator console
Configures and supervises the backend. Secrets stay in the Keychain.
On the headset
The session client
Where the work happens. Threads, an editor, Git review, and diagrams in the room around you.
Why it runs on your Mac
An agent that is useful on your codebase needs your codebase, your logins, your Keychain, and your build tools. Shipping all of that to someone else's machine for a nicer client is a bad trade.
The headset removes the other limit. A monitor shows you two or three files at once. In the room, the conversation, the diff, the file tree, and the plan each get a place.
The cost is a Mac that is awake and on the same network as the headset.
What you can do in it
Threads that persist
Assistant text, reasoning, tool activity, diffs, and token usage. Restart anything and the conversation is still there.
A real editor
Browse, search, and edit files in a bundled Monaco editor.
Git review in place
Status, staging, commit, pull, and push. Fixed operations, never command strings.
Diagrams in the room
SVG, Mermaid, and editable spatial diagrams stored as ordinary files in your workspace.
Bring your own agent
AgentRoom drives the agents you already use.
Claude Code
Uses the login already on your Mac
Codex
Point it at the executable
Cursor
Sign in. Turns bill your Cursor plan
DeepSeek Harness
Supply the runtime and credentials
External agents speaking Agent Client Protocol can be registered too. That path ships switched off.
How it fits how we work
Three claims, each with something you can check.
Transparency
We publish the limits, not only the features.
Registering a folder does not sandbox it, and the optional terminal is unsandboxed once launched. Both are written down.
Trust and safetyAccountability
Dangerous settings are absent, not filtered.
A path to an executable is remote code execution by configuration, so no connected client can set one.
ArchitectureIntegrity
The defaults cost us the demo.
The terminal, editor language services, and external agents all ship off. Each looks better on, and each stays off.
What ships switched offWhere it is now
Open beta. The visionOS client is on TestFlight and the Mac app comes with it. Expect rough edges. The backend and Mac app are intended for public release, with no date until it is real.