unknown

openclaw dropped a good update and this one is super important for your swarm, but half the features don't work until you manually activate them.

>ACP thread-bound agents 

i was already spinning up subagents in Discord threads to handle tasks. it worked, but i had to manage it myself by checking if they finished, cleaning up dead threads, etc. 

now openclaw handles all of that. the agent opens a thread, does the job, reports back...i only show up when an actual decision needs to be made.

→ do this: set spawnAcpSessions: true in your discord channel config

>external secrets management  

my API keys, anthropic, elevenlabs, brave etc, were just sitting in a config file in plain text. 

anyone with access to that file had the keys. now they live in a separate vault and only get loaded when the system actually needs them.

→ do this: run openclaw secrets audit — it scans your config and tells you exactly which keys are still exposed and where

>agent routing CLI 

wiring agents to channels used to take a lot of time. now it's just bind/unbind from the cli, so onboarding a new agent takes a minute or even less..

→ do this: migrate with openclaw agents bind <id> --channel <your-channel> --peer <target>

you have to do all of the above because openclaw ships opt-in features, not auto-changes...

anything that touches security, permissions, or routing requires you to do it manually, and these are super important for your swarm.

PS: if you're not on Discord, the ACP thread stuff doesn't apply, but the other two do.

Peter Steinberger 🦞

A retweet referencing an update to 'openclaw' with implications for swarm configurations, noting that several features require manual steps to activate. The content is truncated and provides minimal detail.