Freestyle Remote for ChatGPT

Every chat gets its own computer.

Pair ChatGPT with persistent cloud workspaces where your repo, tools, and running processes are ready to go. One conversation. One isolated Freestyle VM.

Set up your workspace See how it works

Early access · ChatGPT desktop on macOS · Node.js 22+

ChatGPT · Project Atlas

New conversation

Track down the checkout regression and open a fix.

Working in your repo

› npm test -- checkout
✓ 18 passing 1 failing
› git diff --stat
src/checkout.ts 12 ++++++------

thread-vm · runningpersistent disk · isolated process space

The 30-second version

ChatGPT brings the reasoning. Freestyle brings the computer. Remote keeps the two connected.

01 / Architecture

From a message to a real machine.

Freestyle Remote appears in ChatGPT as a paired remote device. A hosted gateway maps each top-level conversation to its own VM and routes tool calls to the right machine.

ChatGPT

You talk, attach context, and approve work from the familiar desktop or mobile interface.

Remote gateway

Authenticates the paired device, remembers thread-to-workspace routing, and brokers short-lived access.

Freestyle VMs

Every top-level chat gets separate files, processes, and durable disk—without competing with your laptop.

Chat A · activeChat B · paused

SOURCE private GitHub repoPREPARE team-private snapshotBOOT clean starting point for new chats

This is routing, not a shared filesystem. Chats cannot casually see one another’s workspaces; deliberate gateway-level recovery is a separate, explicit operation.

02 / Lifecycle

Disposable compute. Durable work.

The machine follows the conversation—not the browser tab. Leave, sleep your laptop, or let the VM pause. When you return to that chat, the same disk and workspace return too.

Prepare once

Setup pairs a remote device and prepares a private snapshot containing the selected repository and project tooling.

Start a chat

A new top-level conversation boots its own VM from that snapshot. Other conversations get other machines.

Pause when idle

Idle compute can stop automatically. The filesystem, thread mapping, and workspace identity remain intact.

Resume in place

Open the original chat and its VM wakes up with edits, dependencies, and long-lived project state still there.

Snapshot updates are intentionally forward-only. Refreshing the repository snapshot improves the starting point for future chats. Existing conversations keep their current VM and local changes. Temporary helper chats work inside the parent chat’s VM rather than creating another durable workspace.

03 / Boundaries

Built to stay out of the way.

The useful mental model is simple: isolation at the chat boundary, persistence at the disk boundary, and credentials managed at the device boundary.

Isolation

Chats don’t collide.

Two conversations can edit the same repository in parallel because each has its own filesystem and process space—not a shared checkout.

Secrets

Configure once.

Device-wide workspace secrets are encrypted in gateway storage and injected over encrypted SSH. Listing secrets returns names, never values.

Retention

Disconnect ≠ delete.

Disconnect stops the remote device, pauses VMs, and revokes its dedicated API key—but retains disks, metadata, and private snapshots for reconnection.

04 / Get connected

Your first remote workspace is one command away.

Run setup inside a GitHub repository. It guides you through Freestyle sign-in, ChatGPT pairing, team selection, and project preparation.

macOSChatGPT desktopNode.js 22+GitHub access

Run in Terminal

npx --yes https://remote.freestyle.sh/npx

The installer uses your normal Freestyle login and walks you through pairing.

01
Connect your accountsAuthenticate with Freestyle, choose a team, and pair the remote device with ChatGPT.
02
Prepare your projectCreate a private, repo-ready snapshot in your Freestyle account.
03
Open ChatGPTStart a conversation in the project. The workspace is provisioned and routed automatically.