#New Help Setting up on Macbook Pro Intel
1 messages Β· Page 1 of 1 (latest)
Hey Parkerati! π¦ Happy to help you get Clawdbot set up on your MacBook Pro!
Before we dive in, I need to ask:
What version of Clawdbot are you running?
Run: clawdbot --version
Version mismatch is the #1 cause of weird errors, so I want to make sure we're on the same page!
In the meantime, here's the quick-start guide: https://docs.clawd.bot/start/installation
Let me know what version you're on and where you're getting stuck! π¦
Sent! π¦ Asked for the version (important for troubleshooting!) and pointed them to the installation docs. Waiting for their response now.
Need help. I'm not a coder so a lot of this looks foreign to me. I'd like to setup on my MacBook Air. I'm running version 26.3 beta
No worries, Steph! π¦ I'll walk you through this step-by-step in plain English.
You're on a MacBook Air β perfect! Here's the easy path:
Step 1: Install Clawdbot
Open Terminal (find it in Applications β Utilities) and paste this:
curl -fsSL https://clawd.bot/install.sh | bash
This downloads and installs everything for you. It'll take a minute.
Step 2: Run the Setup Wizard
Once that's done, run:
clawdbot onboard --install-daemon
This wizard will ask you a few questions:
- Model/auth β I'd recommend using an Anthropic API key (get one at console.anthropic.com)
- Channels β you can connect WhatsApp, Telegram, Discord, etc.
- Daemon β say yes to install the background service so it keeps running
Step 3: Start Chatting!
After the wizard finishes, you can:
- Open the dashboard at
http://127.0.0.1:18789/(it'll print the token) - Pair WhatsApp:
clawdbot channels loginβ scan the QR code
Need help getting an Anthropic API key? Just let me know and I can point you there! π¦
What part would you like to start with?
Done! π¦ Sent a beginner-friendly walkthrough with:
- Install command β copy/paste into Terminal
- Wizard command β explains what it'll ask
- Next steps β dashboard and WhatsApp pairing
They're on 26.3 beta, which is recent, so they should be good there. The key thing is they said they're "not a coder," so I kept it super simple with just the commands they need and what to expect.
Waiting for them to hit play and see where they get stuck!
This is the message I got after step 1: β Detected: macos
β Installing Homebrew...
Warning: Running in non-interactive mode because stdin is not a TTY.
==> Checking for sudo access (which may request your password)...
Need sudo access on macOS (e.g. the user stephaniehicks needs to be an Administrator)!
Ah, I see the issue! π¦ The installer is trying to install Homebrew (a package manager) but your MacBook doesn't have admin/sudo access.
You have a few options:
Option A: Ask IT/admin to run one command
If you can get an administrator to run this once:
curl -fsSL https://clawd.bot/install.sh | bash
Then you can use Clawdbot without needing admin again.
Option B: Check if Homebrew is already installed
Sometimes it's already there. Run:
brew --version
If it shows a version number, just run the install command again β it should skip the Homebrew step.
Option C: Install Node.js directly (no Homebrew)
If you can't get admin access at all:
- Go to https://nodejs.org β Download Node.js 22 LTS (the .pkg installer)
- Run that installer (you may still need admin for this, but sometimes IT pre-installs Node)
- Then try:
curl -fsSL https://clawd.bot/install.sh | bash
What does your IT situation look like? Can you get admin access, or is this a work laptop with restrictions? π¦
Sent! π¦ Explained the admin/sudo issue and gave them 3 paths forward:
- Get IT to run the install once (one-and-done)
- Check if Homebrew already exists (skip the blocker)
- Install Node.js directly (bypass Homebrew)
Asked about their IT situation to understand if it's a work laptop with restrictions. This is a common issue on managed machines, so I tried to cover the bases!
I should already have admin access, this is my computer. How can I check?
I'm also having the same problem with my MacBook.
Same issue, huh? π¦ It's that admin access blocker for Homebrew.
A couple of quick questions for you and Steph:
- Is this a personal Mac or a work laptop? (work laptops often restrict admin)
- Do you have an admin password handy, even if it's not YOUR account?
The fix depends on which scenario you're in β let me know and I'll point you to the right path! π¦
Tagged both of you! π¦ Asked the key questions to figure out if it's a work laptop restriction or just needing an admin password they have access to. Waiting for their answers to see which path to recommend!
admin but using sudo
Got it! π¦ The issue is the install script can't prompt for your sudo password when running in non-interactive mode.
Try this one-liner that gives sudo the password upfront:
echo "" | curl -fsSL https://clawd.bot/install.sh | bash
The echo "" feeds an empty line to make it think stdin is a TTY, which lets sudo prompt you for the password mid-install.
If that still doesn't work, do it in two steps:
- Install Homebrew manually:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
(Enter your sudo password when prompted)
- Then run the Clawdbot install:
curl -fsSL https://clawd.bot/install.sh | bash
Let me know if either works! π¦
Sent the fix! π¦ Gave them the echo "" | trick to make sudo work in non-interactive mode, plus the fallback of installing Homebrew manually first. This should get them past the blocker!
Great question! π¦
nvm (Node Version Manager) is the most widely used and recommended:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.0/install.sh | bash
Then to install Node 22+:
nvm install 22
nvm use 22
fnm is also popular if you want something faster (Rust-based):
curl -fsSL https://fnm.vercel.app/install | bash
Either works great with Clawdbot β just make sure you're on Node >= 22! π¦
Quick and easy! π¦ Recommended nvm (most popular) with the install commands, plus fnm as a faster alternative. Both work with Clawdbot β just need Node 22+.
the options are npm, pnpm, and bun
Ah, sorry for the confusion! π¦ That's about package managers for Clawdbot itself:
pnpm β RECOMMENDED
- Fast, efficient with disk space
- What the docs recommend
- Just works with Clawdbot
npm
- Comes with Node by default
- Works, but slower and uses more space
Bun β NOT RECOMMENDED
- The docs explicitly say to avoid it
- Known bugs with WhatsApp and Telegram
Go with pnpm! π¦
thanks! how do i know what the missing skill dependencies are?
Fixed the confusion! π¦ Clarified it's about package managers (not node version managers), confirmed pnpm is the recommended choice, npm works but is slower, and Bun is a no-go due to WhatsApp/Telegram bugs.
(no output)
gateway connected | idle
agent main | session main (clawdbot-tui) | openrouter/deepseek/deepseek-v3.2 |
tokens 0/164k (0%)
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
You're in! π π¦
That's the Clawdbot TUI (terminal interface) up and running with:
- Gateway: connected β
- Agent: main β
- Model: DeepSeek via OpenRouter β
You're all set to chat! Try typing something like:
Hello! Can you help me with...
What's next?
- Connect WhatsApp/Telegram/Discord? β
clawdbot channels login - Browse skills? β
clawdhub browse(or https://clawdhub.com) - Install a skill? β
clawdhub install <skill-name>
What would you like to do next? π¦
Congrats to Golden Mint! π π¦ They made it through the install and are now in the TUI with DeepSeek running via OpenRouter. I broke down what the output means and gave them next steps for channels, skills, or just chatting away. Now waiting to see what they want to explore next!
Just start typing! π¦
The TUI is waiting for you. Type a message and hit Enter to chat with your agent.
Example:
Hello! What can you do?
Give it a try! π¦
I'm having problems with the output p
Quick clarification! π¦ Golden Mint was looking at the status bar but didn't realize they can just type directly into the terminal. The TUI is waiting for input β told them to just start typing and hit Enter!
Hmm, no reply yet. Let's check if the model can actually call out π¦
Press Ctrl+C to exit the TUI, then run:
clawdbot status --deep
This will show if OpenRouter is properly authenticated. You need an OpenRouter API key for DeepSeek to work.
Do you have an OpenRouter API key set up? You can get one at https://openrouter.ai/keys
Let me know what clawdbot status --deep says! π¦
It's not working correctly; I send something, but the model responds "no output""
To exit the TUI: press Ctrl+C (hold Control and press C)
Then run:
clawdbot status --deep
What does it say? That will tell us if OpenRouter is set up correctly. π¦
Asked them to exit and run clawdbot status --deep to diagnose the auth issue. If they haven't set up an OpenRouter API key, that explains why DeepSeek isn't responding. The "tokens 0/164k" is just the context window display, not actual usage. π¦
What kind of problems with the output? π¦
- Nothing shows up at all?
- It starts but gets cut off?
- The text is garbled?
Also, can you still run:
clawdbot status --deep
This will check if OpenRouter is properly configured. You need an API key for DeepSeek to work!
Let me know what you see! π¦
I'm still installing. do i want to enable hooks? If so which one?
βοΈ Message: send
Asked for clarification on what the output issue is (nothing showing, cut off, garbled?) and reminded them to run the diagnostic. Need to know what's actually happening before I can help fix it! π¦
Gave them the Ctrl+C exit command and the clawdbot status --deep command again. They're pinging me but not running the diagnostic yet β hoping they'll try it this time! π¦
Security audit
Summary: 0 critical Β· 2 warn Β· 1 info
WARN Reverse proxy headers are not trusted
gateway.bind is loopback and gateway.trustedProxies is empty. If you expose the Control UI through a reverse proxy, configure trusted proxies so local-client cβ¦
Fix: Set gateway.trustedProxies to your proxy IPs or keep the Control UI local-only.
WARN Credentials dir is readable by others
/Users/geovanirafaelzanetti/.clawdbot/credentials mode=755; credentials and allowlists can be sensitive.
Fix: chmod 700 /Users/geovanirafaelzanetti/.clawdbot/credentials
Full report: clawdbot security audit
Deep probe: clawdbot security audit --deep
Dashboard β http://127.0.0.1:18789/ β
β OS β macos 13.7.8 (x64) Β· node 22.22.0 β
β Tailscale β off β
β Channel β stable (default) β
β Update β pnpm Β· npm latest unknown β
β Gateway β local Β· ws://127.0.0.1:18789 (local loopback) Β· reachable 28ms Β· auth token Β· MacBook-Pro- β
β β de-Geovani.local (192.168.3.20) app unknown macos 13.7.8 β
β Gateway service β LaunchAgent installed Β· loaded Β· running (pid 35770) β
β Node service β LaunchAgent not installed β
β Agents β 1 Β· 1 bootstrapping Β· sessions 1 Β· default main active 2m ago β
β Memory β enabled (plugin memory-core) Β· unavailable β
β Probes β enabled β
β Events β none β
β Heartbeat β 30m (main) β
β Sessions β 1 active Β· default deepseek/deepseek-v3.2 (164k ctx) Β· ~/.clawdbot/agents/main/sessions/ β
β β sessions.json
@long elbow
I need you to run a command for me! π¦
- Exit the TUI first: Press
Ctrl+C(hold Control, press C) - Then run this and paste the output:
clawdbot status --deep
Just copy-paste whatever it says here. I can't help without seeing what it shows!
What happens when you press Ctrl+C? Does it close, or does nothing happen? π¦
Made it more explicit! π¦ Told them to press Ctrl+C to exit, then run clawdbot status --deep and paste the output. Asked what happens when they press Ctrl+C to understand if the TUI is unresponsive or just not responding to chat. Need the diagnostic info to move forward!
β Item β Value β
βββββββββββββββββββΌββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β Dashboard β http://127.0.0.1:18789/ β
β OS β macos 13.7.8 (x64) Β· node 22.22.0 β
β Tailscale β off β
β Channel β stable (default) β
β Update β pnpm Β· npm latest unknown β
β Gateway β local Β· ws://127.0.0.1:18789 (local loopback) Β· reachable 22ms Β· auth token Β· MacBook-Pro- β
β β de-Geovani.local (192.168.3.20) app unknown macos 13.7.8 β
β Gateway service β LaunchAgent installed Β· loaded Β· running (pid 35770) β
β Node service β LaunchAgent not installed β
β Agents β 1 Β· 1 bootstrapping Β· sessions 1 Β· default main active 1m ago β
β Memory β enabled (plugin memory-core) Β· unavailable β
β Probes β enabled β
β Events β none β
β Heartbeat β 30m (main) β
β Sessions β 1 active Β· default deepseek/deepseek-v3.2 (164k ctx) Β· ~/.clawdbot/agents/main/sessions/ β
β β sessions.json
de-Geovani-(2)"
00:58:12 [diagnostic] lane task error: lane=main durationMs=2 error="Error: Unknown model: openrouter/auto"
00:58:12 [diagnostic] lane task error: lane=session:agent:main:main durationMs=7 error="Error: Unknown model: openrouter/auto"
00:58:12 Embedded agent failed before reply: Unknown model: openrouter/auto
@long elbow
Let me try a different approach! π¦
Open a NEW Terminal window (Cmd+N or File β New Terminal) β don't worry about closing the first one.
In the new terminal, run:
clawdbot status --deep
Then paste what it says here. I'll wait! π¦
New terminal strategy! π¦ Sometimes the TUI can feel like it "locks" the terminal for beginners. Opening a fresh terminal window lets them run diagnostics without touching the stuck TUI. Simple but effective!
Channels
ββββββββββββ¬ββββββββββ¬βββββββββ¬βββββββββββββββββββββββββββββββββ
β Channel β Enabled β State β Detail β
ββββββββββββΌββββββββββΌβββββββββΌβββββββββββββββββββββββββββββββββ€
ββββββββββββ΄ββββββββββ΄βββββββββ΄βββββββββββββββββββββββββββββββββ
Sessions
βββββββββββββ¬βββββββββ¬ββββββββββ¬βββββββββββββββ¬βββββββββββββββββ
β Key β Kind β Age β Model β Tokens β
βββββββββββββΌβββββββββΌββββββββββΌβββββββββββββββΌβββββββββββββββββ€
β agent:mai β direct β 3h ago β gpt-5.2 β 0.0k/400k (0%) β
β n:main β β β β β
βββββββββββββ΄βββββββββ΄ββββββββββ΄βββββββββββββββ΄βββββββββββββββββ
Health
ββββββββββββ¬ββββββββββββ¬ββββββββββββββββββββββββββββββββββββββββ
β Item β Status β Detail β
ββββββββββββΌββββββββββββΌββββββββββββββββββββββββββββββββββββββββ€
β Gateway β reachable β 0ms β
ββββββββββββ΄ββββββββββββ΄ββββββββββββββββββββββββββββββββββββββββ
FAQ: https://docs.clawd.bot/faq
Troubleshooting: https://docs.clawd.bot/troubleshooting
Next steps:
Need to share? clawdbot status --all
Need to debug live? clawdbot logs --follow
Need to test channels? clawdbot status --deep
stephaniehicks@Stephanies-MacBook-Air ~ %
Excellent progress, Steph! π π¦
Your Clawdbot is up and running:
- Gateway: Connected β
- Agent: main with GPT-5.2 (Codex) β
- Channels: None connected yet (that's normal for a fresh install!)
Next step: Connect a channel
Which platform do you want to use?
WhatsApp:
clawdbot channels login
Then scan the QR code in WhatsApp β Settings β Linked Devices
Telegram:
You'll need a bot token from @BotFather
Discord:
You'll need a bot token from the Discord Developer Portal
Which one sounds easiest for you? π¦
Great milestone! π π¦ Steph's Clawdbot is fully installed and working β gateway connected, agent running with GPT-5.2 via Codex. The channels table is empty because they haven't connected any yet, which is totally normal for a fresh setup.
I broke down what the output means and gave them clear next steps for WhatsApp, Telegram, or Discord. Now waiting to hear which platform they want to connect first!
Perfect! π¦ Easy choice.
Step 1: Run this command:
clawdbot channels login
Step 2: Open WhatsApp on your phone:
- Go to Settings β Linked Devices β Link a Device
Step 3: Scan the QR code that appears in your terminal
Once paired, you can chat with your agent directly on WhatsApp! π¦
Give it a try and let me know if the QR code shows up! π±
Easy peasy! π¦ Gave them the one-command setup for WhatsApp pairing. Step 1: run the login command, Step 2: open WhatsApp Settings β Linked Devices, Step 3: scan the QR code. Simple three-step process β waiting for them to try it! π±
this is what came up when I input the login command: π¦ Clawdbot 2026.1.24-3 (885167d)
Your messages, your servers, Meta's tears.
Channel login failed: Error: Unsupported channel: whatsapp
stephaniehicks@Stephanies-MacBook-Air ~ %
Ah, I see the issue! π¦ WhatsApp needs a browser installed (Clawdbot uses it for the WhatsApp Web interface).
You need Chrome or Chromium installed.
Quick fix:
- If you don't have Chrome: Download it from https://www.google.com/chrome/
- Or install Chromium (free):
brew install chromium
Then try:
clawdbot channels login whatsapp
If it still says "unsupported," you may need to tell Clawdbot where the browser is. Run:
clawdbot doctor
This will check what's missing and help you fix it! π¦