On this page
AgentRoomInstall guide

Install AgentRoom and pair your Vision Pro

Join the AgentRoom TestFlight beta, set up the backend on your Mac, register a folder, and connect the headset over your local network.

AgentRoom is in open beta on TestFlight. This page covers what you need, how to join, and how to get from a fresh install to a first agent turn.

Read trust and safety before you point AgentRoom at a repository you did not write.

What you need

Requirement
MacmacOS 14 or later, awake, on the same network as the headset
HeadsetApple Vision Pro running visionOS 26
NetworkBoth devices on the same local network
AgentAt least one coding agent configured. Claude Code is the quickest, because it uses the claude login already on that Mac

There is no account to create with us and nothing to upload. The Mac does the work.

Join the beta

The visionOS client is distributed through TestFlight:

Join the AgentRoom beta on TestFlight

Open that link on the Vision Pro, or on an iPhone signed into the same Apple Account, and TestFlight will install the build. You will need the TestFlight app, which is free from the App Store.

The macOS operator app is provided alongside the beta rather than through the App Store, because it supervises a local server and stores credentials in your Keychain. The beta instructions cover how to get it.

Set up the Mac

The macOS app is the operator console. Everything on this list happens there.

  1. Configure an agent. Pick one from the agents AgentRoom drives. Claude Code needs the least setup: if you already use it on that Mac, AgentRoom can use that login. Codex needs a path to its executable. Cursor needs a web sign-in through the bundled SDK.

  2. Create a bearer token. The backend binds to your local network so the headset can reach it, which means a token is not optional in practice. Create one in the Mac app; it is stored in the Keychain.

  3. Register a folder. This is the folder an agent will work in. Registration is explicit and per-folder. AgentRoom will not touch anything you have not registered.

  4. Start the backend. The Mac app launches and supervises it. It listens on port 8787 and binds to all interfaces so the headset can find it.

To check it is running, open http://localhost:8787 on the Mac. There is a debug page there, and a health check at http://localhost:8787/health.

Connect the headset

Open AgentRoom on the Vision Pro and enter your Mac's address.

On a physical headset, use the Mac's Bonjour hostname or its address on the local network:

http://your-mac.local:8787

You can find the hostname in System Settings under Sharing, as the local hostname. Paste the bearer token when prompted.

The simulator connects to http://localhost:8787 by default and needs no address entered.

Provider keys stay on the Mac. Do not put them on the headset; nothing on the headset asks for them.

Your first turn

Open a workspace, start a thread, and send a turn. You should see assistant text, reasoning, tool activity, and any plan or diff the agent produces stream in as it works.

Threads persist. You can close the app, restart the Mac backend, and come back to the same conversation. If an agent cannot resume a thread after a restart, AgentRoom tells you in a system message on that thread rather than quietly starting a new conversation under the old name.

If it does not connect

  • Check both devices are on the same network. A guest network or a VPN on either device will break this.
  • Check the Mac is awake. A sleeping Mac is an unreachable backend. Check your energy settings if it keeps dropping.
  • Try the address in Safari on the headset. If http://your-mac.local:8787/health does not load there, the problem is the network or the hostname, not AgentRoom.
  • Use the LAN address if Bonjour fails. Some networks block .local resolution. The Mac's local network address works too.
  • Check the token matches. A wrong token fails every mutating request while leaving the health check working, which looks like a connection problem but is not.

Where next