Skip to content

Use Workspace on your computer and phone

Workspace is RunWield in your browser. Your repository, tools, and agents run on your computer; your phone opens the same Sessions. You can start in the TUI, continue on your phone, and return to the TUI.

All terminal commands below run on the computer that holds your repository.

Install RunWield and configure a model provider using the Quickstart. You should be able to run wld and get a reply in your project. Workspace uses those same credentials.

In a terminal on your computer, run:

Terminal window
wld workspace serve

This starts Workspace at http://127.0.0.1:8787 and opens your browser. Keep this terminal running. One Workspace server can show multiple projects.

The first visit shows Authorize this browser, a device label, and a short code.

  1. Give the browser a recognizable label, such as Laptop Chrome.

  2. Copy the command shown on the page.

  3. Run it in a second terminal on the same computer, using your actual code:

    Terminal window
    wld workspace pair ABC123

The browser opens Workspace automatically after approval. It remembers the pairing across visits. A new browser or cleared cookies require pairing again.

Open ProjectsLink a Project. Enter the absolute path to your repository in Project root, optionally give it a display name, and click Link Project.

For example, use /Users/alex/code/my-app on macOS or /home/alex/code/my-app on Linux. This is the path on the computer running Workspace, including when you enter it from your phone. Run pwd in your repository if you need the path.

Your project and its Sessions now appear in the sidebar. Open a Session or choose New Session to start one.

Tailscale Serve gives Workspace an HTTPS address reachable from your Tailscale devices. Set this up once on the computer running Workspace.

Install Tailscale on your computer and phone, sign in to the same account, and turn it on on both devices. On your computer, check that the CLI works:

Terminal window
tailscale status

If the command is missing, follow the Tailscale CLI setup.

On your computer, run:

Terminal window
tailscale serve --bg --https=443 127.0.0.1:8787

If Tailscale asks you to enable HTTPS, follow the link it prints and then retry the command. Copy the resulting https://…ts.net address. You can display it again with:

Terminal window
tailscale serve status

The output should look like this, with your computer’s actual name:

https://my-laptop.example.ts.net (tailnet only)
|-- / proxy http://127.0.0.1:8787

The --bg option keeps Tailscale’s forwarding running after this command exits. It does not start RunWield.

If the local Workspace server is still running, press Ctrl+C in its terminal first. Then run this command, replacing the example URL with the exact HTTPS address from step 2:

Terminal window
wld workspace serve --public-origin https://my-laptop.example.ts.net --no-open

Leave this terminal running. It should print Owner Workspace: followed by your HTTPS address.

Use that HTTPS address on both your computer and your phone now. Once configured this way, Workspace expects that address; the old http://127.0.0.1:8787 browser URL will show a Host error. The listener still uses port 8787 locally.

Open the HTTPS address in your phone’s browser. On Authorize this browser, give it a label such as My phone, then run the displayed wld workspace pair CODE command in a second terminal on your computer.

The phone should open Workspace and show the projects you already linked. Bookmark the address or add it to your home screen. Your laptop browser also needs a one-time pairing at this new address.

  1. On your computer, run wld from the linked repository and send a message.
  2. In the TUI, enter /name Phone test to make this Session easy to find.
  3. Leave the TUI open. On your phone, open Phone test in the project’s Session list. You should see the same conversation.
  4. Send the next message from your phone. The reply should also appear in the TUI.
  5. Send another message from the TUI and check that it appears on your phone.

You can also begin with New Session in Workspace, then run wld from that repository and use /resume to open it in the TUI. A truly empty Session is hidden from lists, so send its first message before looking for it elsewhere.

While the agent is working, Steer changes its direction and Queue schedules a follow-up after the current turn. Pending steering and queued follow-ups belong to the screen where you sent them; they do not need to move with you.

Press Ctrl+C in the Workspace server terminal to stop it. Start it again with the same wld workspace serve command you used above. Linked projects and browser pairings are remembered.

For phone access, keep your computer awake, Workspace running, and Tailscale connected on both devices. A sleeping or powered-off computer cannot run your Sessions.

Tailscale forwarding stays enabled until you turn it off. To disable the forwarding created by this guide:

Terminal window
tailscale serve --bg --https=443 off

See the Tailscale Serve command reference for more options.

What you see What to check
Address already in use Another Workspace server is using port 8787. Stop it in the terminal where you started it before starting another.
Host or Origin is not allowed Use the exact URL passed to --public-origin, including https://. Restart Workspace if you changed the address.
Phone cannot connect Check that the computer is awake, both devices have Tailscale connected, and tailscale serve status points to 127.0.0.1:8787.
Bad Gateway / 502 Tailscale is reachable, but Workspace is not. Start the Workspace server and check its terminal for errors.
Pairing code expired Refresh the pairing page and run the new command on the computer running Workspace.
Repository or Session missing Link the repository under Projects, check its absolute path, and send a first message if the Session is empty.