Every step. Every button. Every gotcha. Built for non-technical students. If you follow this in order, you will have a working AI agent connected to Discord.
You need an active Claude Pro or Max plan before you install anything else. The free tier cannot run Claude Code.
Open claude.ai in your browser. If you don't already have an account, sign up. Use an email you'll remember — you'll sign in again during Claude Code install.
Click Upgrade (usually top-right of the sidebar).
Write down the email address on your Claude account. You'll need it in Part 3. If you already forgot which one — go to claude.ai → click the bottom-left avatar → Settings → Account. It's listed there.
One command installs everything you need: bun, Claude Code, and the Discord plugin.
Step 1: Open Terminal. Press Cmd + Space, type Terminal, press Enter.
Spotlight search showing "Terminal" as the top result. Icon: black box with a small >_ in white.
Screenshot to be added before launch.
Step 2: Paste this entire line, press Enter:
The script narrates itself. You'll see lines like:
Step 1: Open PowerShell as Administrator. Click Start → type PowerShell → right-click the result → Run as administrator → Yes.
Step 2: Allow scripts (first time only):
Answer Y to the prompt.
Step 3: Run the installer:
Fully quit your terminal and reopen it. This is the step people skip. It matters.
Cmd + Q (not the red X — a real quit)Install errored halfway? Post a screenshot of the red error text in the Cohort 2 Telegram group. Don't re-run blindly — Code wants to see the error before you try again.
This is where you meet your agent.
~/cohort2-workspace/ for you, with a starter CLAUDE.md inside. You don't need to create the folder — just go there and launch.In your fresh Terminal window, paste this one line:
On Windows, use:
Your browser pops open a Claude sign-in page.
CLAUDE.md in whatever folder you launch from. That file defines your agent's persona and rules. Launching from somewhere else means no persona loaded — your agent goes generic.Use the email on your Claude Pro/Max account (the one you noted in Part 1, Step 3).
After sign-in, return to your terminal. It should show:
That > at the bottom is your prompt. Anything you type there talks to Claude.
Means your terminal didn't pick up the install. Fix: fully quit terminal (Cmd+Q on Mac, close window on Windows), reopen, try again.
Means the setup script didn't finish cleanly. Re-run it: curl -fsSL https://setup.coachreemteam.com/setup.sh | bash (Mac) or iwr -useb https://setup.coachreemteam.com/setup.ps1 | iex (Windows). The script is safe to re-run — it skips anything already done.
Prove it's actually working. 30 seconds.
At the > prompt, type this exact sentence (it's English, not code):
Press Enter. Claude Code will ask for permission to write a file. Type y, press Enter.
Open Finder (Mac) or File Explorer (Windows). Navigate to your Desktop → cohort2-workspace. There's a file called hello.txt. Open it.
That's a working AI agent. It read your English, translated it into a file operation, asked permission, and did the work.
/exit and press Enter. You're back at the regular terminal prompt. To come back in, type claude.Your agent lives in Claude Code. To talk to it from anywhere, give it a Discord presence.
In your browser, go to: discord.com/developers/applications
Sign in with your Discord account if it asks.
The Developer Portal home page with your applications list. Top-right shows a New Application button.
Screenshot to be added before launch.
Click the New Application button (top-right).
A popup asks for a name. This is your bot's name. Pick anything — you can change it later. Examples: "Scout", "MyAgent", your first name.
Check the "I agree to Discord's Developer Terms of Service" box.
Click Create.
On the left sidebar, click Bot.
Scroll down slightly. You'll see a "Token" section with a Reset Token button.
The Bot page showing the Token section with a "Reset Token" button highlighted in red.
Screenshot to be added before launch.
Click Reset Token. Confirm the dialog. A long string appears — this is your bot token.
Stay on the Bot page. Scroll further down to Privileged Gateway Intents.
Toggle ON all three:
Left sidebar → OAuth2 (not "Installation" — the one below it).
Scroll down to URL Generator.
Under Scopes, check the box for bot.
A new section called Bot Permissions appears below. Check these:
URL Generator page with "bot" scope checked, and the four permissions highlighted.
Screenshot to be added before launch.
Scroll to the very bottom. There's a Generated URL box. Click the Copy button next to it.
Open a new browser tab. Paste the URL. Press Enter.
Discord shows a page: "Add a bot to a server." The dropdown should default to a server you own or admin.
You should see "Authorized" confirmation.
Open Discord (web or desktop). Go to the server you invited your bot to.
Click the Members icon (top-right of Discord — looks like two people).
Scroll through the list. Your bot should appear, probably showing as offline (grey dot). That's fine for now — we'll turn it on in Part 6.
Wire the bot token into Claude Code so your agent starts listening.
If Claude Code is still running, skip to step 2. If not, in your cohort2-workspace folder, type claude and press Enter.
At the > prompt, type (replacing YOUR_TOKEN_HERE with the long string you copied in Part 5, Step 3):
Press Enter. Claude Code saves the token, writes a .env file, and reports:
You should see:
Switch to Discord. Click your server. Open the Members list. Your bot should now show a green dot (online).
Three most common causes — check in order:
/reload-plugins again./doctor in Claude Code. If it mentions bun, quit Claude Code (/exit), close terminal (Cmd+Q), reopen, run the setup command again./discord:configure NEW_TOKEN → /reload-plugins.Lock the bot to your Discord user so random people can't DM it.
In Discord, find your bot in the Members list. Click its name.
A popup appears with a Message button (or a chat input at the bottom). Send any message — "hey", "yo", "test".
Within a few seconds, the bot replies with a pairing code (6-8 digits or letters).
Back in your terminal at the Claude Code prompt:
Replace YOUR_CODE_HERE with the code the bot sent you. Press Enter.
Claude Code confirms:
In Discord, DM the bot again. Type something real like:
The bot thinks for a few seconds and replies through Claude Code. You just talked to your agent from Discord.
/loop polling (required for Discord replies)The single most important step for Discord users. Skip this and your bot shows online but goes silent forever.
> prompt by default. Without /loop, incoming DMs accumulate with no handler. You see "typing..." in Discord, then nothing. Ever. This one missing command cost 60 minutes of debugging in our beta test — do not skip.If you closed Claude Code after Part 7, reopen it:
At the > prompt, type:
Claude Code will ask what you want to loop on. Paste this (replace [BOT NAME] with your actual bot name, e.g. "Casha"):
Press Enter. Claude Code enters polling mode. You'll see "loop wakeup" messages appearing every ~60 seconds — that's the session actively checking for new Discord messages.
In Discord, DM your bot: "are you there?"
Within 10-30 seconds, you should see a real conversational reply in Discord. If you see "typing..." followed by an actual message, you're done.
/loop runs only while this Claude Code session is alive. Close Terminal = loop stops = bot goes silent again. To keep it running 24/7 you need tmux or a cloud VPS — we cover that in Week 2./loop but Discord still shows "typing..." with no replyThree things to check in order:
reemteam-check (exit first with /exit, run it from the shell, then re-launch claude). Confirm all layers green — especially Layer 3 (bun in system PATH)./discord:access status — your Discord user ID should be listed in allowFrom./loop — sometimes the first polling directive needs a restart.Prove everything works before Day 1. Takes 60 seconds.
Exit Claude Code (/exit) to get back to a shell prompt. Then run:
You'll see a pass/fail report for every layer of your stack. Anything red prints the exact fix command next to it. Re-launch Claude Code (cd ~/cohort2-workspace && claude) when you're done.
Go to setup.coachreemteam.com/mentorship/verify and fill out the short form. Describe any issues in the Blockers field — Code will reply on Telegram within 30 min to unstick you.
If everything passes, you're cleared for Day 1. See you Wednesday.