You work in the Claude desktop app: you describe what you want in plain English, it builds, and you review. Here's the day-to-day — plus a couple of habits that keep it smooth.
You work through the Claude desktop app connected to your personal cloud workspace — one environment with every app you have access to inside.
Open the Set up my computer guide and paste the single command. It installs everything, signs you in, and builds your workspace. Add it to Claude Desktop once as an SSH connection (codespace@localhost / port 2222)(cs.<your-workspace>.main, port empty) — saved in the app after that.
Run irm rivent.dev/connect | iex in PowerShell and leave the window open (~15s). See Connect Claude Desktop.
On Mac there's nothing to run each session — Claude Desktop connects to your workspace directly.
In Claude Desktop, connect to your workspace, then in Select Remote Folder type /workspaces and pick your app (terminal, podcast, lpflow) — experiments sit one level down, in /workspaces/experiments/<name>. Then say what you want — e.g. "work on Terminal."
You talk to Claude in plain English, like giving instructions to a capable teammate. You never write code — you describe, review, and decide.
Want to see your change running? Just ask Claude to show you — it starts the app for you; you don't need to know any commands. Not sure how something works? Ask it to explain.
Three commands carry ideas from "thought" to "shipped" — plus a quick read on where everything stands. Reach for them especially when several things pile up.
Recommendation: when a bunch of ideas hit you at once, don't fire them off one by one — capture each one. It keeps them organized, makes sure each gets thought through and designed before it's built, and nothing gets lost. Then execute builds them in a tidy batch. A pile of ad-hoc "also do this" requests gets messy fast; capturing first avoids that.
Full command reference lives on How we build → The commands →
You build on the app's safe copy (Dev) and the finished change crosses to the live app (Production) through one reviewed gate. New to that two-copies idea? Start here covers it →
✅ You ship it yourself
Publish once the automatic checks pass
🔒 Waits for Shawn
Code-owner review before it can go live
Plan what's next on the app's Plan tab — a simple Inbox → Up next → In progress → Done board built right into the portal. Cards can hold notes and file / image / PDF attachments. No GitHub, no leaving the portal.
Everyone works on a separate copy, so many people can build at once without clashing. You ship normal work yourself on green CI. Shawn is pulled in only for database changes and production config — where a mistake could hit real data.
Sometimes a feature needs to store something new — a new field on a form, a new list, a new kind of record. That's a database change. You don't do anything special: describe what you need and Claude builds it, on practice data. But a database change is one of the few things that pauses for Shawn's review before it can go live, because real data is involved — Claude opens it for his sign-off automatically.
One thing to know: adding new fields is routine. Changing or removing existing ones is handled more carefully — with a backup — because real data is involved. Claude follows that rule for you.
/capture each, then /execute.← Start here — the five-minute overview.