Put the AI to work β€” right on your own computer

What is this?

You've probably used Claude in a web browser β€” you ask it things, it writes back. That's handy, but it can only talk.

PackClaude is the same AI running on your own computer, where it can actually do the work for you β€” not just describe it. It's the exact setup Roby uses to run his websites, keep his books, manage his real-estate business, and juggle a pile of side projects.

Claude in a browser

Answers questions. Gets slow and forgetful once a chat runs long β€” and can't touch your computer, files, or accounts.

PackClaude (on your computer)

Takes real action β€” builds, edits, automates. Keeps memory in organized files, so it never bogs down or "runs out of room." Works across all your stuff.

It's invite-only, and you don't need any tech skills. If you can copy, paste, and take a screenshot, you can do this β€” Claude itself helps you through every step.

Two heads-ups before you start: the version of Claude that runs on your computer needs a paid Claude plan (about $20/month β€” a free account can't run it), and you'll need a Windows or Mac computer (a phone won't work β€” though you can request access from your phone and finish on a computer later).

1Request accessRoby reviews and approves you. Start here.

βœ… Sent! Roby will review and approve you, then email you a link to finish. Meanwhile, go ahead and do Step 2 β€” you can be all set up by the time he adds you.

Don't worry about GitHub or any of that yet β€” Claude walks you through it after you're approved.

2Get Claude onto your computerLet the AI install everything for you β€” no skills needed.

  1. Get a free Claude account at claude.ai and open a new chat.
  2. Copy the message below, paste it into that chat, send it. Claude becomes your patient install guide.
Paste #1 β†’ into claude.ai
You are helping me, a non-technical person, install everything I need to run Claude Code (the version of Claude that works on my own computer) inside a program called VS Code. Be my patient, step-by-step guide.

>>> MOST IMPORTANT RULE: Give me ONLY ONE small step at a time. Then STOP and wait for me to say "done" (or ask a question) before you give the next step. NEVER give me a numbered list of many steps at once β€” a big list overwhelms me and I will get lost. One step, then wait. <<<

Other rules:
- First ask me β€” playfully β€” whether I'm on "a PC, or a stupid Mac." That's Roby's running joke, so deliver it with a wink and a grin (teasing, never mean); if I'm a Mac user, feel free to keep gently ribbing me about it β€” it's all in good fun. Wait for my answer.
- If I'm on a Mac: BEFORE downloading VS Code, help me find out my chip so we get the right version. Have me click the Apple menu (top-left corner) then "About This Mac," and tell you whether it says "Chip: Apple M..." (that's Apple Silicon) or shows an "Intel" processor. Then have me download the matching Mac build β€” or simplest, the "Mac Universal" download, which works on ANY Mac. (Downloading the wrong one gives a confusing "not supported on this Mac" error, so get this right first.) REMEMBER my chip β€” the SAME choice applies to the Node.js download later: if I'm on an Intel Mac, make sure the Node download dropdown/option is switched from "Apple Silicon"/ARM64 to "Intel"/x64 before I download it, or it won't run.
- Then help me install these, IN ORDER, ONE AT A TIME, confirming each works before we move to the next: (1) VS Code, (2) Node.js (the LTS version), (3) the Claude Code command-line tool, (4) the Claude Code VS Code extension. Don't mention step 2 until step 1 is done.
- IMPORTANT β€” when VS Code first opens, it may pop up asking me to sign in (to GitHub or Microsoft) to "sync settings," with buttons like "Continue with GitHub" / "Continue without signing in." Tell me to SKIP it β€” click "Continue without signing in," or just close the popup with the X. We do NOT sign into GitHub at this popup. The one GitHub login I actually need happens LATER, ONCE, when you run it for the Claude tool (`gh auth login`). Signing in at this early popup opens a confusing browser login that collides with that real step, so tell me to skip every VS Code sign-in nag for now.
- For each single step: give me the exact click-by-click or the exact thing to copy and paste, tell me how to check it worked, and if I hit an error, fix it with me before moving on.
- Assume I don't know what a "terminal" is β€” show me how to open one inside VS Code.
- If I paste you a screenshot, use it to see exactly where I'm stuck.
- Keep it simple and encouraging. Explain any word I might not know.

When all four are installed and I can open a terminal in VS Code and type  claude  to start it, tell me I'm done with this part and should wait for Roby's approval email to finish.

⭐ Your secret weapon: the screenshot

Now that you've got Claude, here's the trick you'll lean on for the rest of the setup: stuck, confused, or staring at an error at any point? Take a picture of your screen and paste it to Claude β€” it'll tell you exactly what to do.

3Wait for Roby's go-aheadHe approves you, then emails you the link to finish.

Once Roby approves your request, you'll get two emails: a GitHub invitation to accept, and a note from Roby with a link to the Finish Setup page. That page has one last thing to paste into Claude β€” and then it takes over: it connects you to Roby's kit, builds your workspace, and starts teaching you. πŸŽ‰

Nothing more to do here for now. Keep an eye on your inbox.