The bait, then the rug-pull.
Five times more productive — that is the opening bid. Alex Finn is not here to read blog posts; he is here to build a working app, hand it off to his phone mid-session, and prove that Claude Code Remote Control is not cloud magic but genuine local execution you can control from the gym.
What the video promised.
stated at 00:12“I'll cover how it works, how to get it set up, how to build your first app, best practices, and when to use Claude Code vs OpenClaw.”delivered at 06:42
Where the time goes.

01 · Hook and feature intro
Productivity claim, feature announcement, agenda callout boxes.

02 · Setup walkthrough
Opens Claude Code in terminal, shows Remote Control docs page, types /remote control for the first time.

03 · V1 Second Brain app
Demo of the built markdown editor at localhost:3000 — creates note, adds folder, discovers drag-and-drop is missing.

04 · Mobile session live
Types /remote control, opens Claude app on phone, prompts drag-and-drop feature from mobile, code executes locally in real time.

05 · Final working app
Back to desktop, drag-and-drop into folders works. Zero-merge return from mobile.

06 · OpenClaw vs Claude Code framework
Chalkboard comparison slide. OpenClaw: quick prototypes, tooling, passive work. Claude Code: big projects, deep work, quick fixes.
Visual structure at a glance.
Named ideas worth stealing.
OpenClaw vs Claude Code Decision Matrix
- OpenClaw: quick prototypes, tooling for OpenClaw, passive work (while sleeping)
- Claude Code: big projects, deep/complex work, quick fixes I need to ship
Clean two-column mental model for choosing between the two tools based on task type and attention level required.
Remote Control Workflow
- 1. Start Claude Code session on desktop
- 2. Type /remote control
- 3. Open Claude app on phone or follow the link in browser
- 4. Prompt from phone — execution stays on your local machine
- 5. Return to desktop — code is already there, no merge needed
Five-step workflow for setting up and using Claude Code Remote Control.
Lines you could clip.
“You're about to become five times more productive.”
“This isn't happening in the cloud. This isn't happening in GitHub. This isn't gonna force me to have to pull down code when I get back to my computer and merge.”
“I'll give it a list of 20 different tasks to do. I'll go to sleep, and it will go down that list while I'm sleeping. Claude code still can't do that.”
“Big, complex, hairy projects that I wanna be hands on with that I wanna guide step by step.”
How they spent the runtime.
Things they pointed at.
How they asked for the click.
“I will also be adding a full deep dive guide on this ClaudeCode mobile experience to the VibeCode Academy and do a live boot camp on it as well. So make sure to click the link down below to join.”
Soft sell — positions the CTA as added value (bootcamp recording) rather than a hard ask. Delivered while still talking through the outro, no pause or tone shift.
Word for word.
The /remote control pattern is a new content format.
Start a build on desktop, hand it to your phone mid-video, finish it from mobile — the workflow IS the content.
- The start-on-computer continue-on-phone arc is a repeatable video structure — not just a feature demo.
- The comparison slide (OpenClaw vs Claude Code) is a standalone shareable asset — screenshot it, post it, drive traffic back to the full video.
- The three-part negation pattern (This isn't X, this isn't Y, this isn't Z) is a clean way to differentiate any tool from its predecessors — steal it for JoeFlow vs transcription SaaS.
- Alex does not do a setup screen or prerequisites section — he goes straight into building. That pacing choice signals trust in the audience and keeps drop-off low.
- The agenda callout (green boxes at 0:42) is a low-cost visual that signals structure without slides. Worth adding to JoeFlow demos.
What this means if you use Claude Code.
You can now pick up any Claude Code session from your phone without losing your local state — no SSH, no cloud sync, no merge conflicts.
- Type /remote control in any Claude Code session to generate a shareable link that opens in the Claude mobile app.
- Everything still runs on your computer — your phone is just the input device. Come back to your desk and the code is already there.
- Best for: continuing deep-work sessions when you have to step away but still have ideas coming.
- Not a replacement for OpenClaw if you want truly async/unattended work — Claude Code Remote Control still requires you to be in the loop.










































































