Problems Installing OpenClaw

The first thing that example 21. Using OpenClaw to Control PiCar-X has you do is to install OpenClaw using:

curl -fsSL https://openclaw.ai/install.sh | bash

I ran this command and I got the message:

OpenClaw installed successfully (2026.10.9)

But then I got the message:

Gateway is not running.

Run `openclaw gateway status --deep` for details.

I ran that command and then got the message:

Service unit not found.

Run: openclaw gateway install

So I ran that command also and it appeared to work with the message:

Installed systemd service: /home/wwindham/.config/systemd/user/openclaw-gateway.service

Gateway service installed. Runtime readiness has not been checked; startup may still be in progress. Check with openclaw gateway status and openclaw health.

Can you tell me what I am supposed to do now to get to the OpenClaw security prompt?

Please try fixing it following the FAQ method: 22. Using OpenClaw to Control PiCar-X — SunFounder PiCar-X Kit documentation

If the issue still persists after following the FAQ steps, please let us know at which step you are stuck and share the full output or a screenshot of the error, along with your Raspberry Pi OS version (the output of cat /etc/os-release). We will then look into it further.

The FAQ was of no help. The only thing in it that applied was about the gateway not running and I had already solved that problem. Consequently, I decided to try running the installation again. This time it completed, but with a very different result from what is shown in the example. Instead of a TUI coming up and asking me if I trust OpenClaw, Chrome came up on the OpenClaw page. From there I was able to do everything shown in the example except set the hooks, so I still need help doing that.

But I have a bigger problem. The section on Prerequisites (for Making OpenClaw Operate the PiCar-X) says:

You can verify the installation by running:


python3 -c "import picarx"

I run the command and there is no error. However, when I try the next step:


cp -r ~/picar-x/picarx-control ~/.openclaw/workspace/skills/

I get the error:

cp: cannot stat ‘/home/wwindham/picar-x/picarx-control’: No such file or directory

Looking in /home/wwindham/picar-x, I see all of the other sub-directories that should be there (example, gpt_examples, etc.), but the picarx-control directory is missing. I would really rather not rerun the entire picar-x installation since I have made so many corrections (especially in the example files). Can I run just the install for the picarx-control directory? I see that there is a install shell script at https://github.com/sunfounder/picar-x/tree/2.1.x/picarx-control.

I managed to figure out how to download the picarx-control files and get them into the right directory. I still need help setting the hooks, but I ran into another problem. Although all of the commands in Testing PiCar-X Skill from the CLI work (except the one to play a sound effect), when I run any of the commands, nothing that I type (or paste) into the terminal appears after that point. That is to say that I can run multiple of these commands, one after the other, and they work, but after the first one, the command does not appear on the screen when I paste another command into the CLI. Even after I abort, nothing that I type in that window appears.

Is this expected behavior? If not then do you have any idea how to fix it? It doesn’t really hurt anything, but it is certainly annoying.

Also, as far as the command to play a sound effect, the command has


/path/to/sound.wav

in it. That’s obviously not a valid path. Are we supposed to change that to something valid, and if so, where because I can’t find a file named sound.wav anywhere?

Will Windham

Thank you for contacting SunFounder technical support, and for describing the issues in such detail.

First, one practical note that may help you a lot going forward: OpenClaw is updated very frequently, and its actual behavior often runs ahead of the official tutorial and FAQ. We have already seen cases where the skills directory structure was changed and the documented steps no longer matched. So if some steps in the tutorial don’t work on your current version, it is quite likely not a mistake on your side — the documentation simply hasn’t caught up yet.

Because of that, our recommended approach is: just ask OpenClaw directly in natural language and let it diagnose and answer for you. The CLI input not displaying and the file path issues both fall into the category of things it can work out itself, and that will be much faster than following the tutorial step by step. To be candid, once you are in the AI-assisted stage, our own development experience becomes less reliable as a reference — many of these behaviors are the AI doing something different from what we expected while still achieving the intended result, and tracing that really depends on the AI itself.

On your specific points:

Setting up hooks: We suggest telling OpenClaw in plain language what you want to achieve and where you are currently stuck, and letting it give you the correct approach for your current version.

Missing picarx-control directory: Glad to hear you already resolved this one, so we won’t go into it further.

Terminal input not displaying: This means the terminal state has been altered by some process (for example, echo has been turned off). Two quick things to try first: type reset and press Enter, or run stty sane; you can also simply close and reopen the terminal. If it is still abnormal, describe the symptom to OpenClaw and let it check which process changed the terminal settings.

Sound file path: The /path/to/sound.wav in the command is a placeholder and needs to be replaced with an audio file that actually exists on your system. As for which path to use, we suggest simply asking OpenClaw — for example, tell it “I need a usable audio file path to play a notification sound; please find the audio files already present on my system and give me the full path.” It will answer based on your actual system, which is more reliable than us giving you a fixed path.

If anything is still unresolved after trying the above, please send us the full output (or error messages) from OpenClaw and we will look into it with you. Thank you for your patience and cooperation.

I don’t expect SunFounder to update their documentation for every little change to OpenClaw, but the change from the old CLI to the current GUI that comes up when you run the installer is night and day different. Consequently, the description in the example is useless. It would be better if SunFounder just deleted that presentation in steps 11 to 17 and simply listed what the user needs to setup. It would also be good if a few words were included in the example about asking OpenClaw if you have a problem or don’t know how to do something.

As far as setting hooks, I asked OpenClaw “How do I set hooks in OpenClaw” and it responded with an explanation about three different types of hooks (internal, plug-in, and web hooks). Fortunately, one of the examples of internal hooks that it showed was “command-logger”, so that gave me what I needed for it. However, it can’t set hooks while the gateway is running, but fortunately OpenClaw is smart enough to realize that and gives you the option of disabling the gateway, setting the hook, and then reenabling the gateway for you. It seemed to do this automatically when I entered the command to set the hook for “session-memory” next. I then tried one of the commands (drive forward) and that worked so it looks like all is good.

As far the sound file path, it’s poor form to include something in a literal string in documentation and not indicate that it’s merely a place holder. SunFounder simply needs to include a sentence before that command in the example stating that, or at a minimum, highlight that part of the command (or better yet do both). It’s not like I am suggesting anything difficult to do and it would help users.

Will Windham

Thanks for the feedback — glad to hear drive forward works and the hooks are set up correctly.

We fully agree with your documentation suggestions and have logged them for the docs team to review:

Remove the outdated CLI walkthrough in steps 11–17 and simply list what the user needs to set up;
Add a note in the example that users can just ask OpenClaw when stuck;
Add a sentence before the sound command stating that /path/to/sound.wav is a placeholder, and highlight that part.
We can’t promise a specific timeline, but your suggestions will be passed on as-is. Thanks for your patience and attention to detail!

I also meant to mention in my previous message that your previous messages had a lot of good information about example 22 that should also be included in the notes.

Will Windham