Connect Your Local Claude Code or Codex to a Cloud Workspace

How it works

One session, two places to drive it

yolo-bridge runs your agent in a terminal on your machine, and you keep typing into it. Prompts sent from the workspace land in the same session, and its screen streams back to the tile.

Nothing connects in

The daemon makes one outbound connection to YOLO Studio and holds it open. Nothing connects in to your machine, and it reconnects on its own after sleep or a dropped network.

Workspace tools included

Claude Code and Codex are wired to the workspace’s tools automatically, through a local proxy that hands them short-lived, scoped tokens. Other terminal agents attach too, without the workspace tools.

A full member of the workspace

Agents in the workspace can send the tile a prompt and read its screen, the same way they work with a cloud agent tile.

Set it up

01
Install
```
curl -fsSL https://yolobridge.sh | sh
```
The installer sets up yolo-bridge with npm. It needs Node.js 20 or later and never uses sudo. npm install -g @yolo-labs/yolobridge installs the same package.
yolobridge.sh
02
Sign in
```
yolo-bridge login
```
Signs you in once, through a link you approve in the browser.
03
Attach
```
yolo-bridge attach
```
Pick a workspace, and yolo-bridge starts Claude Code and attaches it as a tile. Add --agent codex to attach Codex instead, and --label to name this machine in the workspace.
04
Detach when you are done
```
yolo-bridge detach
```
Ends the attachment. yolo-bridge status shows whether you are attached and which paths are approved.

Files and trust

The agent’s screen streams to the tile, so what it shows is visible in the workspace. Files are different: they are uploaded only when pushed from your side. yolo-bridge share uploads a file you name, and the cloud cannot ask the daemon to read a path. The attached agent can send files only from paths you have approved with yolo-bridge allow.

That approval list prevents accidents. It is not a security boundary: the agent runs as your user and has a shell, the same as when you run it without yolo-bridge. When you want a hard boundary, run the agent in a cloud workspace instead, where it is sandboxed in its own virtual machine.

Questions

Does it work with agents other than Claude Code and Codex?

Other terminal agents attach with --agent and the name of their command. Claude Code and Codex get the workspace tools wired automatically; other agents run without them.

What happens when my laptop sleeps?

The daemon reconnects after sleep or a network drop. While the machine is asleep the agent on it is paused too, so work that should keep going overnight belongs in a cloud workspace.

Is the source available?

Yes. yolo-bridge is MIT-licensed, with a public mirror at github.com/yolo-labs-hq/yolobridge.

Keep reading

yolo-bridge yolo-bridge on GitHub Guide: move a local project to the cloud Guide: run Claude Code remotely

Try it on your own repository

Get started

Connect the coding agent on your machine to a cloud workspace