OpenClaw - Local Agent Runtime with Slack Integration and Policy Controls
**People:** David **Idea:** Testing OpenClaw as a self-hosted agent runtime that connects LLM agents to Slack with multi-agent routing, tool permissions, and security controls baked in. **Details:** - OpenClaw runs in a docker container and gives you channel integrations, tool execution, policy controls, and session memory out of the box - Set up a single Slack app with two routed agents - a main admin path for me and a restricted trusted path for other users - Trusted agent is locked down to workspace-scoped read operations and Slack messaging only - DM access uses an allowlist model so only specific Slack users can interact with the bot - Elevated permissions are gated to a single admin user for dangerous operations like exec - Chat commands (bash, config, restart) are disabled globally as an extra safety layer - Group channels are also on allowlist and require an @mention to trigger the bot, preventing accidental activations and bot-loop issues - Channel config works more reliably with channel IDs than human-readable channel names - Host command execution goes through an approval flow in the Gateway UI before anything runs - The architecture separates identity-based access, privilege levels, tool minimization, and execution control - which is the right pattern for multi-user Slack deployments
- Additionally we were able to get the Claude/GitHub interaction in Slack to work in tandem with the OpenClaw bot - being able to gather data from people and Claude/GitHub and send/summarize for another user