#2015 mac, need some assistance pls

1 messages · Page 1 of 1 (latest)

normal lotusBOT
#

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

dire windBOT
#

@static crag If the Gateway logs show the run finishes, but the Safari chat UI stops typing and never shows the assistant message, it’s usually one of these:

  1. Safari/old macOS browser compatibility (UI loads, but some modern JS/WebCrypto/stream bits fail silently)
  2. Control UI assets/protocol mismatch (common on source installs or partial upgrades — UI can’t parse the newer gateway events)
  3. You’re opening the dashboard over non-local HTTP (LAN IP / tailnet IP) and the browser blocks device identity / pairing, so the websocket/events can get weird

Quick “fastest win” checks

  1. Open the Control UI in Chrome or Firefox (same URL) and try the same message.

    • If it works there, this is almost certainly Safari/old macOS. Safari on older macOS versions is… touchy with modern Vite-built SPAs.

  2. Make sure you’re opening it locally on the Mac running the gateway:

    • http://127.0.0.1:18789/ (preferred)
    • Or run openclaw dashboard and use the tokenized link it prints.

  3. Run Doctor (this often fixes “UI says nothing but logs look fine”)
    Doctor will rebuild the Control UI if the protocol schema is newer:

# 
   openclaw doctor
   openclaw gateway restart

Docs for reference:

If it’s still broken, paste these (they’re the quickest to diagnose)

After reproducing once (send a message, see it “finish” with no reply), paste:

  1. openclaw --version
  2. openclaw status --all (safe-ish to share; redacts tokens)
  3. In Safari: Develop → Show JavaScript Console and paste any red errors.
#

Also tell me: macOS version on that 2015 Mac, and whether you installed OpenClaw via npm global or git/source.

#

@static crag Yep — you can skip the browser UI entirely.

Talk to it in the terminal (recommended for your case)

  1. Make sure the gateway is running:
openclaw gateway
# (or if you installed the daemon:)
openclaw gateway restart
  1. Open the terminal UI:
openclaw tui

That gives you a full chat experience in-terminal and avoids Safari/UI weirdness entirely.

#

Docs: https://docs.openclaw.ai/tui and CLI ref: https://docs.openclaw.ai/cli/tui

If openclaw tui connects but you still get “it ran but no reply”, then the issue is not Safari — it’s model/auth/runtime. In that case run:

openclaw --version
openclaw models status
openclaw logs --follow

Then hook it up to Telegram (no UI needed)

  1. Create a bot token via @BotFather.
  2. Set Telegram in config + restart:
openclaw config set channels.telegram.enabled true
openclaw config set channels.telegram.botToken "123:abc"
openclaw gateway restart
#
  1. Check it’s up:
openclaw channels status
  1. DM your bot in Telegram. By default DMs are pairing-gated, so approve the code:
openclaw pairing list telegram
openclaw pairing approve telegram <CODE>

Telegram docs: https://docs.openclaw.ai/channels/telegram

#

@static crag OpenClaw doesn’t need one specific model — it just needs one model that resolves + is allowed + you have auth for (that becomes agents.defaults.model.primary).

The confusing bit: OpenClaw expects model names in its provider/model format (and it enforces an allowlist), so raw marketing names like “1.5 flash / 1.5 pro” often won’t match what OpenClaw is expecting.

Do this during/after onboarding (no guessing)

On the Mac, run:

openclaw models status
openclaw models list --provider google

Pick one of the exact IDs shown there (cheapest one is usually what you want for “barebones”), then set it:

openclaw models set <provider/model-from-the-list>