OpenClaw

[creative567145]

@andreasdueren Thank you, much appreciated.
Soon I'll test Zai, Ollama and Mattermost

Here is something possibly useful.
On our OpenClaw installation via DokPloy, we installed SearXNG on the same VPS.
And we were able to configure it to be able to perform the web searches directly via it. So zero API cost towards Brave/Perplexity.

The Docker Compose value that we added was this one:
SEARXNG_URL=

Perhaps somebody else would wish to apply the same configuration. It would be beneficial if it's also added. Thanks again

[JLX89]

Is there a way to install Tailscale by chance? I'm seeing the documentation, but seems even /app/data is set to an RO file system if trying to install it.

[andreasdueren]

@JLX89 updated to include the Tailscale CLI + daemon installed in the Docker image

To use it, add to /app/data/.env:

TS_AUTHKEY=tskey-auth-...
TS_HOSTNAME=openclaw

@creative567145 added the SEARXNG_URL= as well env

[JLX89]

@andreasdueren Thank you so much!!

[creative567145]

Thank you @andreasdueren

Here are more env variables in case if people wish to use them:
Fast_io_API_Key=
Cloudflare_API_key=

Since version 3.23, there have been a lot of updates to the today's version: 4.9 which includes the Dreaming ability of OpenClaw

@andreasdueren we understand that this is a community package and we are all very grateful for your help. Could we get some info on the intended updates window...example once per 1-3 months or similar. No pressure

[robi]

Self updates would be nice in such a fast moving dynamic app.

[creative567145]

@robi that would be nice, but very risky if many use it.

From what I can notice, in every 2-5th update, there are modifications added that are causing breakage.

So perhaps the most stable way is for @andreasdueren to push updates occasionally (example once per 1-3 months), but perform tests on his own OpenClaw and if needed modify the package so that all instances don't break when an update is automatically pushed.

[robi]

@creative567145 said:
From what I can notice, in every 2-5th update, there are modifications added that are causing breakage.

Really? Break how?

I haven't been using it, but know millions of others are.

Odd that it hasn't been solved by now.

[creative567145]

@robi In the GitHub repository the breaking changes are listed
https://github.com/openclaw/openclaw/releases

Example (from our current version 2026.3.23 to the current one 2026.4.11):
openclaw 2026.4.5
openclaw 2026.4.2
openclaw 2026.3.31
openclaw 2026.3.28
openclaw 2026.3.24

Plus regular upgrades to the system functionality, for example how the Videos are being generated.
But this is due to the setup that each client has performed before that.
For example, to be able to generate Videos via Gemini, we had to install custom skills and scripts. So when the update is applied that doesn't have that requirement, either that functionality will break the current process, or we will just need to re-adjust the configuration.

Many people have reported that they are performing the breakage fixes just by connecting Claude Code via SSH and letting it do it's "magic".

[robi]

@creative567145 thanks for the info, yes that would be the easiest way.

Sounds like they need to manage flavors