proper harness
Hi Krill — I’m troubleshooting an OpenClaw setup on Windows and found a repeatable issue involving plugins.allow.
Current situation
The gateway and Discord work normally with the baseline config.
However, as soon as I add plugins.allow to openclaw.json and restart the gateway, Discord stops loading entirely.
This is not just a login failure:
the gateway still starts
webchat/control-ui still works
but Discord no longer appears in startup logs
and openclaw status --deep no longer shows Discord as an active channel
What we already fixed successfully
Before this, we had several issues and cleaned most of them up:
cron jobs failing because Discord delivery had no explicit recipient
stale minimax-portal-auth plugin config
ACPX runtime failure
For ACPX, we eventually got it healthy and logs now show:
acpx runtime backend ready
So ACPX appears functional now.
The remaining problem
The only change that repeatedly breaks Discord is adding plugins.allow.
Reproduced with:
and also with:
Observed behavior after restart
gateway starts normally
webchat connects
hooks load
ACPX may still be ready
but no Discord startup lines appear
Discord disappears from openclaw status --deep
Rollback behavior
If I restore the previous config backup and restart:
Discord comes back immediately
provider starts normally again
Question
Is there a known issue or special requirement for plugins.allow on Windows, especially when using:
bundled/path-loaded plugins
ACPX
Discord channels
In short:
Adding plugins.allow seems to stop Discord from bootstrapping, even though the rest of the gateway still starts normally.
We wanted to clean up this warning without breacking discord:
plugins.allow is empty; discovered non-bundled plugins may auto-load...
Any guidance on the correct/safe way to use plugins.allow here would help a lot.
loud vessel