#Help with install

1 messages · Page 1 of 1 (latest)

astral harness
#

Hi guys! I just tried to install clawdbot on my mac mini but I'm having issues getting started. I followed the guide with the recommended install, completed the wizard, created my telegram bot but I can't get anything to run. When the wizard finished it tried to open my dashboard but I also got:

This site can’t be reached
127.0.0.1 refused to connect.

My gateway install failed and I am not able to get it working. I ran clawdbot doctor and this is what I get

Gateway ───────────────────────╮
│ │
│ Gateway daemon not installed. │
│ │
├─────────────────────────────────╯
│
◇ Install gateway daemon now?
│ Yes
│
◇ Gateway daemon runtime
│ Node (recommended)
│
◇ Gateway ────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Gateway daemon install failed: Error: launchctl bootstrap failed: Bootstrap failed: 5: │
│ Input/output error │
│ Try re-running the command as root for richer errors.

Tried to ask claude code and search google but none worked. Can anyone help me please?

tawny summitBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

hoary basaltBOT
# astral harness Hi guys! I just tried to install clawdbot on my mac mini but I'm having issues g...

Hey icharlie17! 🦐 That launchctl bootstrap error is a macOS permissions thing. Here are a few things to try:

1. Run as root for the richer error message:

sudo clawdbot gateway install

2. If that still fails, try cleaning up first:

# Unload any existing service
sudo launchctl unload /Library/LaunchDaemons/bot.clawd.gateway.plist 2>/dev/null

# Then reinstall
sudo clawdbot gateway install

3. Check if you have Full Disk Access:

#
  • System Settings → Privacy & Security → Full Disk Access
  • Make sure your terminal has it enabled

4. Alternative: Run gateway manually instead of as a daemon:

clawdbot gateway start

This bypasses launchctl entirely and runs it in your terminal session.

The dashboard won't work until the gateway is running, so focus on getting that sorted first. Let me know which step gets you further!

astral harness
#

I ran the 4 steps. none worked. this is the output of the commands

sudo clawdbot gateway install
Password:

🦞 Clawdbot 2026.1.20-2 (cb7791c) — Give me a workspace and I'll give you fewer tabs, fewer toggles, and more oxygen.

error: too many arguments for 'gateway'. Expected 0 arguments but got 1.
❯ sudo launchctl unload /Library/LaunchDaemons/bot.clawd.gateway.plist 2>/dev/null

❯ sudo clawdbot gateway install

🦞 Clawdbot 2026.1.20-2 (cb7791c) — One CLI to rule them all, and one more restart because you changed the port.

error: too many arguments for 'gateway'. Expected 0 arguments but got 1.
❯ clawdbot gateway start

🦞 Clawdbot 2026.1.20-2 (cb7791c) — iMessage green bubble energy, but for everyone.

error: too many arguments for 'gateway'. Expected 0 arguments but got 1.

hoary basaltBOT
#

Give those a shot! 🦐

astral harness
#

they all seemed to throw an error but ran again clawdbot gateway and worked apparently.

I go to the dashboard and get this error

disconnected (1008): unauthorized: gateway token missing (set gateway.remote.token to match gateway.auth.token)

hoary basaltBOT
astral harness
#

it worked! I tried talking to my telegram bot and got

Clawdbot: access not configured.

Your Telegram user id: REDACTED

Pairing code: REDACTED

Ask the bot owner to approve with:
clawdbot pairing approve telegram <code>

hoary basaltBOT
astral harness
#

Embedded agent failed before reply: No API key found for provider "anthropic". Auth store: /Volumes/OWC/.../.clawdbot/agents/main/agent/auth-profiles.json (agentDir: /Volumes/OWC/.../.clawdbot/agents/main/agent). Configure auth for this agent (clawdbot agents add <id>) or copy auth-profiles.json from the main agentDir.

hoary basaltBOT
astral harness
#

Im trying to configure my claude code credentials but not working

Long-lived authentication token created successfully!

Your OAuth token (valid for 1 year):

REDACTED

Store this token securely. You won't be able to see it again.

Use this token by setting: export CLAUDE_CODE_OAUTH_TOKEN=<token>

│
◇ Claude Code CLI OAuth ───────────────────────────────────────────────────────────╮
│ │
│ No Claude Code CLI credentials found in Keychain ("Claude Code-credentials") or │
│ ~/.claude/.credentials.json.

hoary basaltBOT
astral harness
#

but I want to use my claude code pro (20$) sub, not the API key

hoary basaltBOT
# astral harness but I want to use my claude code pro (20$) sub, not the API key

Ah, that's a bit different! Unfortunately, Claude Code Pro's OAuth token doesn't work as an API key for Clawdbot — they're separate authentication systems.

Your options:

  1. Buy an Anthropic API key (from console.anthropic.com) — this is the simplest and what Clawdbot expects

  2. Try using Claude Code CLI directly with Clawdbot — there's experimental support for using codex (Claude Code CLI) as a model provider. You can set it up with:

    clawdbot models add claude-code --command "codex"

    This requires Claude Code CLI to be installed and authenticated on your machine.

The API key route is definitely the smoother experience. If you want to try the Claude Code CLI route, let me know and I can help you configure it! 🦐

astral harness
#

I want to use my claude code cli. I select antropic and get 4 options. how do I proceed

hoary basaltBOT
astral harness
#

error: unknown option '--command'

hoary basaltBOT
# astral harness error: unknown option '--command'

Unfortunately, in your version (2026.1.14), there's no built-in option to use Claude Code CLI as a model provider. The models auth setup-token only supports Anthropic directly.

Your options:

  1. Get an Anthropic API key from https://console.anthropic.com/settings/keys — this is the supported path

  2. Check for updates — maybe a newer version added Claude Code CLI support:

    clawdbot update run

The API key route is the most reliable right now. Let me know what you'd like to do! 🦐

astral harness
#

I have the latest claude-code version just installed it
2.1.14 (Claude Code)

hoary basaltBOT
astral harness
#

2026.1.20-2

hoary basaltBOT
# astral harness 2026.1.20-2

Perfect! 🎉 You're now on 2026.1.20-2.

Now try using your Claude Code CLI again. You should have better support now. Try:

clawdbot models auth setup-token --provider anthropic

Or check what options are available:

clawdbot models auth --help

Let me know what you see! 🦐

astral harness
#

Manage model auth profiles

Options:
-h, --help display help for command

Commands:
add Interactive auth helper (setup-token or paste token)
login Run a provider plugin auth flow (OAuth/API key)
setup-token Run a provider CLI to create/sync a token (TTY required)
paste-token Paste a token into auth-profiles.json and update config
login-github-copilot Login to GitHub Copilot via GitHub device flow (TTY required)
order Manage per-agent auth profile order overrides
help display help for command

hoary basaltBOT
astral harness
#

clawdbot models auth login

🦞 Clawdbot 2026.1.20-2 (cb7791c) — I keep secrets like a vault... unless you print them in debug logs again.

Error: No provider plugins found. Install one via clawdbot plugins install.
❯ clawdbot plugins install

🦞 Clawdbot 2026.1.20-2 (cb7791c) — I'm the reason your shell history looks like a hacker-movie montage.

error: missing required argument 'path-or-spec'

hoary basaltBOT
astral harness
hoary basaltBOT
astral harness
#
  1. Token must come from Claude Code CLI, not Anthropic Console
  • Run
    claude setup-token
    (not from anthropic.com console)
  • The token is a setup-token string, not an API key
  1. Token needs to be on the gateway host

  • If you generated the token on another machine, paste it on the gateway host:

    clawdbot models auth paste-token --provider anthropic

  1. Check the auth profile mode
  • Run
    clawdbot models status
    to see if auth is configured correctly
  • Profile
    anthropic:claude-cli
    must have mode
    "oauth"
    (token mode rejects OAuth credentials)