Apps move Experiment → Incubating → Operational. The whole framework — dev app, dev database, CI, previews, the plan board, approvals — is built while an app is Incubating, with production built but dark. Going live flips it on.
Runs on real data in its own database, from day one. Backed up nightly; gates arrive at go-live.
Throwaway. Dev data only, no production. Promote it or let it lapse.
A card lives on its app's own Plan board — this tab shows the same cards together: filter, search, drag between columns, tick the circle to complete in place, click to edit. New cards are added on an app's board, or from any Claude Code session ("add a todo to Terminal's inbox").
One line per app — click a line for its latest changes. Changes land on an app's dev version; Shawn publishes dev → live from each app's board.
Parked thoughts and half-formed ideas live on the Idea Board →
Nothing here is scheduled. A card becomes a task the moment it moves onto an app's Plan board.
Everything you need to go from zero to shipping. Read how it works, do the one-time setup, connect your first project — then you're working. About 10 minutes the first time; seconds every day after.
The Codespace is your environment — a cloud computer with the app running. Claude Desktop is your interface — you connect it to that workspace and build by talking. Nothing runs on your laptop; production data never reaches you.
Open rivent.dev and sign in with your @slw.vc email. Bookmark it — it's the front door to every project.
GitHub builds a cloud workspace from the repo's .devcontainer — dependencies and dev-database wired up, identical for everyone. It runs on practice data; production is never injected. You never open the browser editor — you reach the workspace through Claude Desktop.
The native Claude app connects to that workspace over SSH. You get the Claude interface, with the real running environment behind it — one place to work.
Tell Claude what you want in plain English. It runs inside the Codespace — sees the real code, runs the app, uses the dev database.
Changes are reviewed before they go live, and the workspace persists — reconnect tomorrow right where you left off.
It installs what's needed, signs you into GitHub (your browser opens — click Authorize, maybe twice), and builds your personal SLW Workspace in the cloud with every app you have access to already inside.
Press the Windows key, type powershell, Enter, then paste:
Open the Terminal app, then paste:
Safe to re-run any time — it repairs whatever's missing.
Download the Claude desktop app and sign in with your own Claude plan (Pro or Max). This is your interface for every project.
Each work session you open a secure link, then pick the app you want.
In PowerShell, run this and leave the window open — wait for the big TUNNEL OPEN box, then minimize it:
This opens the tunnel that lets Claude Desktop reach your workspace. Closing it (or a reboot) disconnects — just run it again next session.
On Mac, Claude Desktop connects to your workspace directly — no command needed. Go straight to the next step.
Click the environment pill (bottom of the Code window) → your SLW Workspace connection. First time only: + Add SSH connection and enter these (also saved on your Desktop as Rivent-Workspace-Connection.txt):
When Select Remote Folder appears, clear the box, type /workspaces, click Go, then click into your app and Select Folder:
You'll only see the apps you have access to. To switch apps later, reopen the folder picker.
Claude runs inside the workspace — it sees the real code, can run the app on the dev database, and makes the change. Your work goes up as a reviewed change; nobody edits the live app directly.
Coming back after a restart? Your workspace, sign-in, and Claude Desktop connection all stay saved — just re-run irm rivent.dev/connect | iex (Windows) to reopen the link, then open Claude Desktop.
Each session: run connect (Windows), open Claude Desktop, pick your app under /workspaces, build.
Builds your workspace. Windows: PowerShell. Mac: Terminal (curl -fsSL rivent.dev/setup | bash).
Run this in PowerShell and leave the window open — wait for the TUNNEL OPEN box. (Mac skips this step.)
Claude Desktop → environment pill → your SLW Workspace connection. On Windows the values are codespace@localhost, port 2222, identity = the path the connect command printed. Then in Select Remote Folder type /workspaces → Go → pick → Select Folder.