What problem does it solve? Adding a messaging channel to OpenClaw requires credentials to be propagated consistently across macOS Keychain, launchd startup scripts, shell environment files, and disaster recovery provisioning, and missing any one of these causes partial setups that fail silently or break on fresh machines. ## Core Features & Use Cases - Seven-Step Secret Pipeline: Stores tokens in macOS Keychain, then mirrors them into openclaw-secrets.sh, openclaw-env.sh, and provisioning secrets.sh so runtime, terminal, and recovery contexts all stay in sync. - Config and Agent Binding: Updates openclaw.json with jq to enable the channel and bind it to a target agent, then deploys with stow and restarts the gateway via launchctl. - Verification and Naming Enforcement: Checks gateway logs for channel connectivity and enforces strict naming conventions for Keychain services, environment variables, and channel IDs. - Use Case: When onboarding a new Slack workspace to an OpenClaw agent, run this pipeline to store both the bot token and socket-mode app token, bind the channel, restart the gateway, and confirm connectivity in one repeatable flow. ## Quick Start Ask the agent to add a Slack channel to OpenClaw for a given agent ID using your bot token and app token, then verify connectivity in the gateway logs.
