00 / 17
The Builder Unlock — a constellation of builder's tools orbiting a glowing cloud

THE BUILDER
UNLOCK

No slides. No theory. Build live.

⏱ ~90 MIN

Bring a beginner's mind. Ask everything twice. When something breaks, paste the error back to Claude — that's the workshop.

OR PRESS SPACE / → @salesforce.com Google sign-in · one click

STEP 01 — OPEN

Open the Terminal

1
⌘ + Space
⊞ Win
press the keys
2
⌕ Terminal ↵
type, then Enter
3
you@MacBook ~ % PS C:\Users\you>
you're in
before the command: Make sure Zscaler is connected and you are signed into Okta. The installer needs that Salesforce network path to reach the LLM gateway.
Don't worry — you got this. If you've never opened the Terminal before, that's fine. It's just a typing window. Same computer, same files. The only difference is you'll be typing commands instead of clicking buttons. A few keys, one Enter, and we're moving.

STEP 02 — INSTALL

Install Claude Code

In the terminal you just opened, paste the command below and hit Enter. 

curl -fsSL https://plugins.codegen.salesforceresearch.ai/claude/install.sh | bash

What you'll see

  • If you don't have Xcode Command Line Tools, a popup asks to install them — click Install, wait ~5 min
  • A browser opens for Salesforce SSO — sign in once
  • When it finishes: open a NEW Terminal window before clicking continue (so PATH refreshes)

In Windows Terminal (PowerShell), paste the command below and hit Enter. Same SF-internal Claude as Mac — LLM gateway, certs, and the support plugin all set up for you. 

irm https://plugins.codegen.salesforceresearch.ai/claude/install.ps1 | iex

What you'll see

  • Pre-install checks (OS, arch, curl, openssl) — ~5 sec
  • If Git for Windows isn't installed, you'll get one Windows UAC prompt (publisher: Johannes Schindelin) — click Yes. That's the official Git for Windows installer.
  • ~12 SF certificates get bundled (you'll see the names scroll by) — that's secure access to the LLM gateway, normal
  • A browser tab opens for Google sign-in — pick your @salesforce.com account → "Sign-in complete"
  • When it finishes: close + reopen Windows Terminal (so PATH refreshes)
requires: Connected to Zscaler + signed into Okta. The installer can't reach the LLM gateway otherwise.
already used Embark? Run the official cleanup first so old provider settings do not override the Salesforce gateway. Cleanup guide

STEP 03 — RESTART

Close that terminal — really close it

Quit the Terminal app completely (⌘ Q), then open a fresh one. Close Windows Terminal completely (Alt+F4 or click the X), then open a fresh one. Without this, your shell won't see claude on its PATH yet.

1

Quit Terminal completely

Close Windows Terminal completely

Press ⌘ Q while Terminal is focused. Don't just hit the red dot — that leaves the shell running, and PATH won't refresh.

Press Alt+F4 or click the X. Make sure no Windows Terminal windows are still open. Don't just minimize — the shell process needs to actually exit.

2

Open a new Terminal

⌘ Space → type Terminal → Enter. You should see a fresh prompt.

⊞ Win → type Terminal → Enter. You should see a fresh PowerShell prompt.

Why we keep saying this. When you install something new, your current shell doesn't know about it yet — only future shells do. The #1 reason people get stuck is skipping this step.

STEP 04 — LAUNCH

Launch Claude Code

Make a sandbox folder first. Claude can read every file in the folder it's launched from — so don't launch it from your home folder. 

mkdir -p ~/claude-projects && cd ~/claude-projects && claude
md -Force ~\claude-projects; cd ~\claude-projects; claude

What you'll see

  • Claude Code starts in your terminal — full-screen UI
  • The welcome banner shows ~/claude-projects as the working directory
  • You'll see "How can I help you today?" as the prompt
Checkpoint · Try it

STEP 05 — TRY IT

First contact

Three quick checks: Claude responds, the gateway looks right, and you can switch models.

Type into Claude:

hello

Then run:

/status

And then:

/model

What you'll see

  • Claude replies in a second or two — you're talking to the model
  • /status shows the Salesforce gateway connection details
  • /model opens an inline picker — Sonnet is the everyday default
  • Choose Opus for the bigger model if you want to token max. It is stronger, slower, and less shy about using tokens.
  • The selected model shows up in the bottom status bar of the Claude UI
  • If something feels off later, /support opens the Salesforce Claude support helper

STEP 06 — INSTALL YOUR TOOLS

Install your tools

Paste each command into Terminal, one at a time. Wait for it to finish before moving to the next one.

Password: (typing won't show — that's normal)
If Terminal asks for your Mac password, type it and press Enter. Nothing will appear while you type. That is normal.

STEP 1install Homebrew + add it to your shell

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" && BREW_BIN="$([[ -x /opt/homebrew/bin/brew ]] && echo /opt/homebrew/bin/brew || echo /usr/local/bin/brew)" && echo "eval \"\$($BREW_BIN shellenv)\"" >> ~/.zprofile && eval "$($BREW_BIN shellenv)"

STEP 2install Heroku + GitHub CLIs

brew install heroku gh

STEP 3connect Slack MCP

claude mcp add -s user -t http --client-id 188160004832.9210129962818 --callback-port 3118 slack https://mcp.slack.com/mcp

STEP 4add Org62 read MCP

claude mcp add --transport http Org62-Sobject-Read https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads --callback-port 8082 --client-id 3MVG9WQsPp5nH_EpM_KnrLdttExiAuzLoaVZkfx52M1ORCimCnoSOKvZzy2bABbcT0dhhi80GJKgFbKkP4Rhf --scope user

Run one command at a time. Close and reopen Windows Terminal between steps.

STEP 1install Heroku CLI and GitHub CLI via winget

winget install Heroku.HerokuCLI GitHub.cli

STEP 2connect Slack MCP

claude mcp add -s user -t http --client-id 188160004832.9210129962818 --callback-port 3118 slack https://mcp.slack.com/mcp

STEP 3add Org62 read MCP

claude mcp add --transport http Org62-Sobject-Read https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads --callback-port 8082 --client-id 3MVG9WQsPp5nH_EpM_KnrLdttExiAuzLoaVZkfx52M1ORCimCnoSOKvZzy2bABbcT0dhhi80GJKgFbKkP4Rhf --scope user

STEP 07 — RESTART

Restart your terminal again

Same drill. The tools you just installed need a fresh shell to land on PATH. Quit Terminal (⌘ Q), open a new one, then cd back to your project folder. Close Windows Terminal (Alt+F4), open a fresh one, then cd back to your project folder.

1

Quit Terminal (⌘ Q) and open a fresh one

Close Windows Terminal (Alt+F4) and open a fresh one

Same trick as before. The tools you just installed need a new shell to be visible.

2

Hop back into your project folder

cd ~/claude-projects

PowerShell handles ~ the same way as Mac/Linux for your home folder.

STEP 08 — AUTHENTICATE

Authenticate Org62 MCP

The approved read-only Org62 MCP is already added from Step 6. Now sign in so Claude can use it.

1

Start Claude from your project folder

claude

If Claude is already open in this folder, stay there.

2

Open the MCP picker

/mcp
3

Select Org62-Sobject-Read

Arrow to the Salesforce MCP server and start the authentication flow.

4

Use custom domain Org62, then click Allow

If the browser does not open automatically, copy the URL from Claude and paste it into your browser.

STEP 09 — CHECK

Check Org62 MCP

Before asking account questions, confirm the Salesforce MCP shows as connected.

1

Open the MCP picker again

/mcp
2

Look for Org62-Sobject-Read connected

If it is disconnected, select it and authenticate again. Port 8082 must be free for the callback.

Checkpoint · Try it

STEP 10 — TRY IT

Ask Salesforce something

Switch back to your Claude Code window and ask it to talk to Org 62. No SOQL needed — ask for the account context you actually want.

Type into Claude:

search org62 for an account named "Acme". Show me the owner, account team, open opportunities, open cases, and any Slack channels that look related.

What you'll see

  • Claude says something like "I'll query Org 62 for that account…"
  • First time only: Claude may ask permission to use Org62-Sobject-Read — approve it
  • Results stream back: owner, team, opportunities, cases, and useful links
  • If nothing comes back, try a broader account name or ask Claude to search by partial match

STEP 11 — CONNECT

Connect Slack

Slack MCP is already added from Step 6. Now authenticate it through Claude.

1

Open the MCP picker

/mcp
2

Select slack

Arrow to the Slack MCP server and start the browser authentication flow.

3

Choose Salesforce Internal, then click Allow

The workspace dropdown may default to Salesforce External. Switch it before clicking Allow.

What you'll see

  • Back in Claude: ✓ slack connected
  • If you see "not authorized to install slack MCP app," the wrong workspace was selected
  • If /mcp still doesn't show slack as connected, fully quit and relaunch Claude (File → Exit, not just the X)
Checkpoint · Try it

STEP 12 — TRY IT

Ask Slack something

Now Claude can search Slack. Start with your own follow-ups, then connect it back to the account context you found in Salesforce.

Type into Claude:

search Slack for DMs I may need to respond to. Summarize the top 5 with links, then look for recent messages in any account channels we found from org62.

What you'll see

  • First time only: permission prompt for Slack tools — pick allow
  • Search results stream back: message previews, channel names, and links
  • Claude summarizes what needs a response and what is just noise wearing a calendar invite
  • Try variations: find the account channel for Acme or summarize what that channel discussed this week

STEP 13 — OPTIONAL

Google Workspace

Optional power-up. Gmail, Calendar, Drive, Docs, Sheets, and Slides as MCP tools are useful, but this path currently requires git.soma access. If you do not have it, skip this step and keep building.

Google Workspace Git.Soma GitHub CLI SF AI Stack

Requires Git.Soma access

Google Workspace plugin path

Not everyone has Git.Soma access today. IT is working on removing this requirement; until then, this is what is needed to get the Google Workspace plugin working.

Get Git.Soma access
Need Git.Soma access? IdentityIQ steps + justification
  1. Go to salesforce.okta.com.
  2. Search for EIP (Enterprise IGA Platform), or open EIP directly.
  3. Click Manage User Access and wait for it to load.
  4. Click your username in the top-left of the grid.
  5. Click Next, then search for Technology-RnD-Access.
  6. Click through the remaining screens.
  7. Paste the business justification below.

Be careful to select exactly Technology-RnD-Access — avoid similarly named options in the list.

I need Technology-RnD-Access to access Git.Soma repositories required for the Salesforce Native AI Stack and Google Workspace MCP workshop setup. This enables approved Salesforce internal AI tooling for Gmail, Calendar, Drive, Docs, Sheets, and Slides during the Builder Unlock lab.

STEP 1authenticate git.soma for the SF AI Stack marketplace

⚠️ Needs Zscaler + Git.Soma access. If this says you are already logged in, keep going. 
gh auth login --hostname git.soma.salesforce.com --git-protocol https --web

STEP 2bootstrap SF AI Stack marketplace

⚠️ Mac/Linux path today. This downloads the marketplace + mcp-adaptor. If you hit a 403, the missing piece is Git.Soma repo access. 
curl -fsSL https://rpm.repo.local.sfdc.net/artifactory/strata-blobs/ai-marketplace/get-plugins.sh | bash

STEP 3install Google Workspace plugin

claude plugin install google-workspace@salesforce-native-ai-stack

STEP 4inside Claude, authenticate Google Workspace

/salesforce-trust-foundations:mcp-auth

STEP 5verify Google Workspace is connected

/mcp

In the MCP list, Google Workspace should show as: plugin:google-workspace:vmcp-google-workspace · ✔ connected · 70 tools

Have a real use case and still stuck?

Checkpoint · Try it

STEP 14 — TRY IT

Build something

Time for the fun part. Build something you actually care about. A simple game is usually the easiest place to start: small rules, fast feedback, and more fun than pretending a landing page is your destiny.

Builder examples

  • Miguel built a math game.
  • Arsenio built a basketball game.
  • Charlie from Latin America built a soccer game.
  • Mark Sullivan, a Regulated Industries leader, built a baseball game.
  • Connor built a polo game.

Type into Claude (replace the bracketed parts with your own passion):

build me a simple browser game about [something I care about]. Keep it playable in one page, make the rules clear, add a score, and open it in my browser when you're done.

What you'll see

  • Claude scaffolds a folder with index.html + maybe style.css
  • You'll see the files appear in your ~/claude-projects folder
  • It opens the game in your browser — that's your idea, running on your machine
  • Keep the first version simple. You can always iterate after it becomes real.

Or try one of these instead:

build me a math game where kids race against the clock to solve simple problems build me a basketball free-throw game with timing, scoring, and a leaderboard build me a soccer penalty-kick game with moving goalie logic build me a baseball pitch-and-hit game with three innings and simple physics

STEP 15 — SHIP IT

You actually did it.

Right now that project only runs on your laptop. Two more sentences and Claude puts it on the internet — a real URL you can text to someone and watch them go "wait, you built this?"

guardrail: Deploy personal projects and safe demos here. No customer data, internal Salesforce knowledge, or confidential content.

Back in your second Terminal window:

heroku login

What you'll see

  • Heroku opens a browser tab — click Log In, done in ~5 seconds
  • Token gets stored in ~/.netrc automatically
  • You're now ready to deploy whatever Claude builds for you

Need Heroku access or deployment guidance?

Heroku access →
Checkpoint · The payoff

STEP 16 — TRY IT

Ship it

Now ask Claude to put your project on the internet. One sentence. Claude wires up git, creates a Heroku app, pushes the code, and hands you a live URL.

Type into Claude:

deploy what we just built to Heroku and give me a public URL I can share

What you'll see

  • Claude adds a Procfile + small server (so Heroku knows how to run it)
  • Permission prompts — review and allow when reasonable
  • It runs git init, heroku create, git push heroku main
  • Final answer: a live *.herokuapp.com URL — click it. Your project is on the internet.
  • Send the URL to a friend. Watch them open it. That's the unlock.

STEP 17 — YOU'RE IN

That's the unlock.

You've installed Claude, wired it into Salesforce, Slack, and Heroku, built something, and shipped it live. Everything from here is just better prompts.

More to try:

show my top 10 open opportunities in org62 — sorted by amount, with stage and close date search Slack for "at risk" or "slipping" in the last 30 days — group what you find by account find accounts in my territory with open opps over $500K and no activity in the last 30 days summarize the last week of activity in [your team channel] — tell me what to follow up on # …and when you're ready for the showstopper: prep me for my 2pm with [account name] — pull their open opps from org62, summarize the last 7 days of activity in their dedicated Slack channel, and draft me a 5-bullet talk track of what to push on

who's next?

You are. Go build something.

STEP 18 — THE CREED

AI-assisted mastery. Human-driven future.

From thinkersto builders.

We don't wait for the future. We build it.

The shift

The old world

We needed people to execute instructions, repeat processes, and optimize efficiency.

The new world

We need builders who ask better questions, experiment, learn, and create new possibilities.

Why it matters

  • AI lowers the cost of execution.
  • Human value shifts to curiosity, judgment, and creativity.
  • The bottleneck is imagination, not information.
  • Builders turn ideas into impact.

The Builder Creed

A mindset for the AI builder era

1

I choose curiosity

I ask questions and seek to understand what's possible.

2

I embrace struggle

I welcome challenges that make me stronger.

3

I experiment fearlessly

I test ideas, fail fast, and learn faster.

4

I keep learning

I am never done growing.

5

I collaborate with AI

I use AI as a partner to amplify my potential.

6

I build impact

I turn ideas into value for others.

7

I empower others

I teach others how to learn so they can build too.

8

I ship and iterate

I build, measure, learn, and build again.

Thank you for your time.
What you built today matters less than the shift you practiced: asking, trying, learning, and shipping.

Think.
Learn.
Build.

Don't wait for instructions.
The future belongs to people who can think, learn, and build alongside AI.

Thinkers imagine. Builders create. Together, we transform.

// crafted by salmanmian.ai · self-serve mode · change