Reference guide for maintaining OpenClaw on a Standard Account.

in

Since you've successfully bypassed the permission restrictions (nice!), these are the commands you'll need to keep it running smoothly.

OpenClaw Maintenance Guide (Standard User)

1. Update OpenClaw

Since you installed with a custom --prefix, the standard openclaw update command might struggle to find its own files. Use this command to update manually:

npm install -g openclaw@latest --prefix=$HOME/.local

Pro Tip: After any update, always run openclaw doctor to migrate your configuration files to the latest version.

2. The "Health Check" Commands

If OpenClaw ever acts up or says "command not found" again, use this diagnostic checklist:

Command What it tells you
which openclaw Verifies the app is in your local folder
openclaw --version Checks if you are on the latest release
openclaw doctor Automatically repairs broken config files
openclaw gateway status Checks if the background service is running

3. Understanding Your Setup

Because you are on a Standard Account, your installation lives in a specific "sandbox" in your home folder. This keeps your system safe and avoids needing an Admin password.

  • Executable Location: /Users/[yourname]/.local/bin/openclaw

  • Configuration Files: ~/.openclaw/openclaw.json

  • Logs & Data: ~/.openclaw/logs/

4. Troubleshooting the PATH (The "Reset" Button)

If you open a new terminal and openclaw doesn't work, your .zshrc might have been overwritten by another app. You can fix it instantly by running:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc

5. Security Best Practices

Since you are running this on a Standard Account (which is the safest way to do it!), remember:

  • Don't use sudo: You should never need to type sudo for openclaw commands now. If a command asks for it, it's trying to touch system files it shouldn't.

  • Keep it Local: If the onboarding wizard asks to bind to 0.0.0.0, always choose 127.0.0.1 unless you specifically need to access it from another device.

OpenClaw macOS Setup Guide (Standard Account)

in

The Problem

Standard macOS accounts do not have "Write" access to /opt/homebrew/bin or /usr/local/bin. When using npm install -g, the installer may claim success but fail to actually place the executable file in a folder your system can see.

The Solution: Local Prefix Installation

Installing to your user's home directory avoids the need for an Admin password and keeps the software isolated to your profile.

1. Perform a Local User Install

Run this command to force npm to install into your personal hidden folder:

npm install -g openclaw --prefix=$HOME/.local

2. Configure your Shell Path

You must tell your terminal to look in that specific local folder before checking the system folders.

  • Open your profile: vi ~/.zshrc

  • Add this line to the very bottom:

export PATH="$HOME/.local/bin:$PATH"

After saving you’ll need to refresh the shell:

source ~/.zshrc

Use these commands to verify the setup:

Command Purpose Successful Result
echo $PATH Checks your search list Should start with /Users/yourname/.local/bin:...
which openclaw Locates the executable /Users/yourname/.local/bin/openclaw
rehash Refreshes command cache No output (clears the "not found" memory)