Installing something generally means you install a program, and the associated configuration.
With Pinokio, in most cases both the program and the config are stored self-contained in the app folder inside pinokio.
However, in some cases--for example when you're installing an engine that can be used by multiple clients (ex: Claude code, Codex CLI, and Openclaw)--the configs are stored globally (while the program is stored self-contained inside pinokio), and this is intentional. This is so that if you already have an app installed, another client can take advantage of the same credentials and configs instantly without having to set up all over again.
TLDR: if you already have OpenClaw installed globally, when you install OpenClaw inside Pinokio, it will install a fresh binary in a self-contained manner INSIDE pinokio, but it will use your already-configured settings from your existing install (or create one if it doesn't exist) at ~/.openclaw. So there will be no conflict.
Installing something generally means you install a program, and the associated configuration.
With Pinokio, in most cases both the program and the config are stored self-contained in the app folder inside pinokio.
However, in some cases--for example when you're installing an engine that can be used by multiple clients (ex: Claude code, Codex CLI, and Openclaw)--the configs are stored globally (while the program is stored self-contained inside pinokio), and this is intentional. This is so that if you already have an app installed, another client can take advantage of the same credentials and configs instantly without having to set up all over again.
TLDR: if you already have OpenClaw installed globally, when you install OpenClaw inside Pinokio, it will install a fresh binary in a self-contained manner INSIDE pinokio, but it will use your already-configured settings from your existing install (or create one if it doesn't exist) at
~/.openclaw. So there will be no conflict.