feat(openclaw): update sandbox with Slack support, expanded policies, WS proxy patch#53
Open
mjamiv wants to merge 1 commit intoNVIDIA:mainfrom
Open
feat(openclaw): update sandbox with Slack support, expanded policies, WS proxy patch#53mjamiv wants to merge 1 commit intoNVIDIA:mainfrom
mjamiv wants to merge 1 commit intoNVIDIA:mainfrom
Conversation
… WS proxy patch - policy.yaml: Add network policies for Anthropic, OpenAI, Google, Telegram, Slack (REST + Socket Mode), GitHub, npm/PyPI, Brave Search, OpenRouter, LinkedIn. Document the Slack wildcard gotcha and tls:skip requirement. - openclaw-ws-proxy-patch.js: New file. Monkey-patches the ws WebSocket constructor to tunnel Slack Socket Mode connections through the OpenShell CONNECT proxy. Required until native WS proxy support lands (see #387). - openclaw-slack-manifest.yaml: New file. Complete Slack app manifest with 23 bot scopes and 12 events for one-click app creation. - Dockerfile: Bump openclaw to @latest, add WS proxy patch and Slack manifest, set NODE_OPTIONS to auto-load the patch. - openclaw-start.sh: Rewrite as a full lifecycle manager with subcommands (start, stop, status, logs, pair). Uses nohup for gateway persistence across SSH disconnects. - README.md: Document all new features, policy coverage, Slack setup guide, WS proxy explanation, and troubleshooting section.
Open
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the
sandboxes/openclaw/directory with battle-tested configurations for running OpenClaw with Slack Socket Mode, multiple LLM providers, and full gateway lifecycle management inside OpenShell sandboxes.Changes
policy.yaml— Expanded network policiesslackandslack_websocketpolicies with documented rationale for the split (tls: skipon WS endpoints prevents the L7 proxy from breaking Socket Mode)*.slack.comwildcard gotcha on OpenShell ≤ 0.0.15openclaw-ws-proxy-patch.js— New filewsWebSocket constructor to tunnel Slack Socket Mode connections through the OpenShell CONNECT proxywslibrary does not natively support HTTP CONNECT proxies for WebSocket upgradesopenclaw-slack-manifest.yaml— New fileDockerfileopenclaw@2026.3.11→openclaw@latestNODE_OPTIONS="--require /sandbox/openclaw-ws-proxy-patch.js"to auto-load the patchopenclaw-start.sh— Rewritten as lifecycle manageropenclaw-start— onboard + start gateway (default)openclaw-start pair CODE— approve Slack/Telegram pairingopenclaw-start stop/status/logs— full gateway managementnohupso the gateway survives SSH disconnectsopenclaw gateway run(foreground mode under nohup) instead of service-manager commandsREADME.mdTesting
These configurations have been tested end-to-end on a live OpenShell deployment with: