Each work session

Connect Claude Desktop to your workspace

You set your computer up once. After that, each time you sit down to work you connect to your workspace and pick the app you want — about two minutes.

Show steps for:

First — done once, ever

If you've never set this computer up, do this first. It builds your personal cloud workspace with every app you have access to already inside.

> irm rivent.dev/setup | iex

$ curl -fsSL rivent.dev/setup | bash

Your browser opens — click Authorize (maybe twice). When it finishes, continue below. Full walkthrough: Start here.

Each work session — 3 steps

Every time you sit down to work

Open your secure link

Press the Windows key, type powershell, Enter, then paste this and leave the window open:

> irm rivent.dev/connect | iex

It wakes your workspace and opens the link. When it says TUNNEL OPEN, minimize the window — don't close it while you work.

Nothing to run on Mac — Claude Desktop connects to your workspace directly. Go straight to the next step.

Connect Claude Desktop

Open Claude Desktop → Code → New → click the environment pill above the message box → your SLW Workspace connection (first time: Add SSH connection and enter these):

SSH Hostcodespace@localhostcs.<your-workspace> — the setup command prints the exact value

SSH Port2222leave empty

Identity fileC:\Users\you\.ssh\codespaces.auto/Users/you/.ssh/codespaces.auto

The exact identity path is printed by step 1 and saved on your Desktop as Rivent-Workspace-Connection.txt.The exact host name and identity path are shown by gh codespace list / the setup output.

Open your project folder

When the Select Remote Folder box appears, clear the path, type /workspaces, and click Go. Click into the app you want, then Select Folder. Experiments aren't in this top-level list — they live one level down, in /workspaces/experiments/<name>:

Folder	App
terminal	Terminal
podcast	Podcast
lpflow	LP Flow
slide-library	Slide Library
dealflow-app	Deal Flow

You'll only see the apps you have access to. Then just tell Claude what you want — "give me an overview of this app" or "run it so I can see it." To switch apps, reopen that folder picker.

💡

That connect command is the one thing you run each session — about 15 seconds, and everything else stays saved. On a personal machine it can even reopen on its own at sign-in; most work-managed laptops block that, so just run the command when you start your day.

💡

On Mac there's no command to run each session — Claude Desktop connects to your workspace directly. Just open Desktop, pick your workspace, and open your app under /workspaces (or an experiment under /workspaces/experiments). If a newly stamped experiment isn't there yet, ask Claude in your workspace: "sync my experiments."

What sticks around vs. what you redo

Shutting down doesn't undo your setup. Almost everything is saved.

Saved — never redo	Redone each session
Your workspace, sign-in, security key, and the saved Claude Desktop connection all persist across reboots.	Just the secure link — the `connect` command (or the auto-start) reopens it. ~15 seconds.

If something's off

✓
Desktop won't connect? Make sure the PowerShell window from step 1 is still open and showed TUNNEL OPEN. If not, run irm rivent.dev/connect | iex again.
✓
Says it timed out or can't find your workspace? It may be asleep — run the connect command again; it wakes it. Give it a minute the first time.
✓
Stuck on one line, going nowhere? A step that sits silent for minutes is a blocked connection, not a slow one — almost always a VPN, a company firewall, or a security prompt hiding behind the window. Press Ctrl+C, disconnect the VPN, allow any ssh prompt you see, then run the command again — it reconnects to the workspace you already have.
✓
Claude says a push failed ("Invalid username or token")? Your GitHub sign-in isn't synced into the workspace yet — run irm rivent.dev/connect | iex again (it re-syncs your sign-in every time, ~30 seconds).
✓
Anything else weird? Re-run irm rivent.dev/setup | iex — it repairs whatever's missing. Still stuck? Send Shawn the PowerShell window and the Desktop error.