AsaleBuying with OpenClaw
OpenClaw speaks whichever wire format it is configured for, which is why it is routed by a path prefix rather than by dialect.
Turning it on
Buy → switch on OpenClaw, pick the models, restart it.
What changes on disk
| File |
|---|
~/.openclaw/openclaw.json |
Backed up before the first write, restored exactly on switch-off.
Why OpenClaw is routed differently
The other tools are told apart by the wire format they speak. OpenClaw cannot be: it speaks whichever format it is configured for, so an OpenClaw request is byte-identical to a Claude Code or a Codex one.
Asale therefore routes it through an explicit /openclaw/… prefix on the local proxy. Without that, OpenClaw traffic would be gated on Codex's switch and handed Codex's model selection — the wrong switch and the wrong models.
This is invisible in normal use. It matters if you are inspecting the proxy URL and wondering why it carries a tool name.
Things to watch
- Its buy switch and model list are entirely its own; turning OpenClaw on does not affect Claude Code or Codex.
- Restart after switching, as with every other tool.