Lobster Shell
All guides

macOS

Install on macOS

Run OpenClaw natively on your Mac with Node.js. The simplest setup for local development and personal use.

Prerequisites

macOS 13 (Ventura) or later
Node.js 18+ (install via brew install node or nvm)
An API key for your preferred LLM provider

Steps

1

Install OpenClaw

Install OpenClaw globally and run the onboarding wizard.

npm install -g openclaw@latest
openclaw onboard --install-daemon

The onboard command will walk you through LLM provider setup, channel configuration, and installing the daemon so OpenClaw starts automatically.

2

Install the Lobster Shell plugin

Use the OpenClaw plugin manager to install directly.

openclaw plugins install @spikelabs/lobster-shell-plugin
3

Restart the gateway

Restart to pick up the new plugin.

openclaw gateway restart

If you installed the daemon, the gateway restarts automatically. Otherwise, stop and re-run: openclaw gateway

4

Open the setup page

The gateway runs on port 18789 by default.

open http://localhost:18789/lobster/setup
5

Connect your account

Click "Connect to Lobster Shell" and sign in at lobstershell.ai. After authorizing, you'll be redirected back with a confirmation.

6

Choose a shell and start chatting

Open your Lobster Shell dashboard, pick a shell, and start a conversation. The avatar will respond with your bot's personality.

Troubleshooting

npm install fails with permission error

Don't use sudo. Instead, fix npm permissions: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally — or use nvm which handles this automatically.

openclaw command not found after install

Make sure your npm global bin directory is in your PATH. Run: npm config get prefix — the bin/ subdirectory should be in your PATH.

Gateway won't start — port 18789 already in use

Another process is using the port. Find it with: lsof -i :18789 — then stop it or configure OpenClaw to use a different port.

Plugin loads but bridge shows 'disconnected'

Check the gateway logs: openclaw gateway logs | grep lobster — the most common cause is a stale OAuth token. Visit /lobster/setup and click Connect again.

Ready to give your bot a face?

Connect your OpenClaw instance and go live with a custom shell in under five minutes.