This installs Claude Code plus the Samba CLI toolchain — gh, gws, wrangler, sf, databricks, jq — and pre-configures your workspace. Idempotent — safe to re-run.
About 8 minutes on a fresh laptop. The installer asks for your password once (Homebrew needs sudo on first install) and auto-discovers your client_secret.json from ~/Downloads/.
client_secret.jsonYour manager will share a Google Drive folder with you. Open it, download the client_secret_<hash>.json file (the filename starts with client_secret), and save it to your ~/Downloads/ folder. That's it — the installer will auto-discover it from there.
If you don't have access yet, ping your manager — it's a one-click share. You can also start the install without it (pick "skip" when prompted) and drop the file in afterwards.
Open Terminal. Run these three commands one at a time. Wait for each to finish before pasting the next.
curl -fL -o /tmp/samba-setup.tar.gz https://github.com/the-sid-dani/samba-onboarding/archive/refs/heads/main.tar.gztar xzf /tmp/samba-setup.tar.gz -C ~cd ~/samba-onboarding-main && ./install.shAbout 8 minutes. The installer asks for your laptop password once (Homebrew needs sudo on first install). After that, walk away — the rest is automatic until the OAuth prompt at step 5, which auto-finds your client_secret*.json in ~/Downloads/.
You need WSL2 first — Windows Subsystem for Linux. One-time setup, then you run the same three Mac commands inside Ubuntu.
The most common Windows failure mode is "nothing happened" after wsl --install. Two causes: (a) PowerShell wasn't opened as Administrator (silent permission fail), or (b) WSL was previously partially-enabled, in which case the command just prints help. Both are covered below. WSL2 install on Windows is real Microsoft software with its own quirks — give it ~10 minutes and one reboot.
PowerShellwsl --install -d UbuntuThe -d Ubuntu flag explicitly requests the Ubuntu distro (not just the WSL kernel). Without it, partial-WSL installs will just print help and exit. The command takes 5–10 minutes — don't close the window. When it finishes, it'll say "Restart your computer to complete installation."
wsl --install -d Ubuntu still says "nothing happened"If the command exits instantly with no progress, WSL is in a weird state. Two fallbacks:
--no-launch: wsl --install -d Ubuntu --no-launch — installs without auto-startingRequired. WSL2 can't finish wiring itself in until Windows restarts.
Click Start, type Ubuntu, hit Enter. A black terminal window opens. What you'll see:
sid). This is your Ubuntu-local username — has nothing to do with your Samba creds.$ prompt with your username and hostname. That's bash inside Ubuntu — Linux now lives inside Windows.If nothing happens when you launch Ubuntu (window flashes and closes, or no prompts appear), the install didn't complete. Open PowerShell-as-admin again and run wsl --status — if it doesn't show a default distro, install Ubuntu from the Microsoft Store and retry.
curl -fL -o /tmp/samba-setup.tar.gz https://github.com/the-sid-dani/samba-onboarding/archive/refs/heads/main.tar.gztar xzf /tmp/samba-setup.tar.gz -C ~cd ~/samba-onboarding-main && ./install.shThe installer's macOS path is heavily exercised; WSL2 path is supported but lightly tested. If a step fails, ping #ai-enablement on Slack with the error message — Sid or someone on the AI Task Force will help unstick. Re-running the installer is safe (idempotent).
The Windows tab can't auto-find your downloaded file because the installer runs inside WSL2. At the OAuth prompt (step 5), pick [1] Paste: open client_secret*.json in Notepad, select all, copy, paste into the terminal, press Ctrl-D.
When the installer finishes, it prints these 5 auth commands at the bottom. Run each one in Terminal (any order) — each opens a browser to sign in with your @samba.tv account. After all five, your CLIs are authenticated.
gh auth logingws auth login -s drive,gmail,calendar,sheets,docs,chat,tasks,slides,formswrangler loginsf org login web --instance-url https://sambatv.my.salesforce.com --alias proddatabricks auth login --host https://dbc-992a5856-b2ed.cloud.databricks.comRun gh auth status and gws auth status. Both should print "logged in" with no errors. If one fails, re-run just that auth command — the others stay authenticated.
Once your tools are installed (above) and your Second-Brain OS is set up (Step 2), open Claude Code and authenticate the integrations that connect it to the rest of your work. samba-onboarding registers Figma, Google Workspace, and Salesforce at user-scope. second-brain-os ships Slack, Atlassian, Figma, and Exa at project-scope (so you need to be inside that folder for those to show up). Each takes one click to authenticate.
Step 3 works best after you've finished Step 2 (Install OS) and have the Second-Brain harness checked out. Running claude below opens a regular Claude Code session, which is fine — the /mcp menu lives at the user level, not the project level — but most teammates do this after Step 2 so they're already inside the harness folder.
claudeIf you're following Step 2 first, cd into ~/Desktop/second-brain-os first so the session opens in the right folder.
/mcpWhat you'll see depends on which folder you launched claude from:
google-workspace-internal, sf-sandbox-fullcopy, figma.mcp.json): slack, atlassian, exa, gemini-visionClick each one and choose Authenticate — a browser tab opens, you sign in with your @samba.tv account, and you're back in Claude in a few seconds. Atlassian/Figma/Exa/Workspace use standard browser OAuth; Slack requires a workspace admin to approve the pre-registered app for your workspace once (one click).
brew — Homebrew package manager (skipped if present)node — Node 20 LTS (pinned for Claude Code compatibility)git, jq — version control + JSON toolingclaude — Claude Code CLI (skills are not bundled; install what you need afterwards)gh — GitHub CLIgws — Google Workspace CLI (Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet)wrangler — Cloudflare Workers CLIsf — Salesforce CLIdatabricks — Databricks CLI~/.databrickscfg~/.config/gws/client_secret.jsongoogle-workspace-internal, sf-sandbox-fullcopy, figma. Visible from any cwd. Registered via claude mcp add-json --scope user.slack, atlassian, exa, gemini-vision. Shipped in the repo's .mcp.json, only visible when claude is launched from inside that folder. Slack uses Anthropic's pre-registered clientId (no per-fork app setup needed); requires workspace-admin one-click approval the first time.