feat(proxy,telegram,container): SNI policy, approval UX, phantom token fix, reload retry#11
Merged
nnemirovsky merged 6 commits intomainfrom Apr 8, 2026
Merged
Conversation
…, Docker API negotiation - Add SNI-based policy evaluation as happy path for IP-only SOCKS5 CONNECT requests on TLS ports. Peeks TLS ClientHello after CONNECT success to recover hostname, re-evaluates policy with it, and populates DNS reverse cache for future connections. Falls back to DNS reverse cache for non-TLS or missing SNI. - Fix timeout message format: CancelApproval now preserves the original approval message text and appends the reason instead of replacing the entire message. Timed-out requests now show what destination was being requested. - Add "Always Deny" button to Telegram approval prompts. Saves a persistent deny rule to the store, same as "Always Allow" does for allow rules. - Reorganize approval buttons into two rows to prevent truncation on narrow screens: [Allow | Deny] / [Always Allow | Always Deny]. - Add /start command handler and register bot commands via setMyCommands API so they appear in Telegram's command menu. - Replace hardcoded Docker API v1.25 with version negotiation. Queries /version on the daemon at startup and uses the reported API version. - Document DNS approval flow design in CLAUDE.md: DNS intentionally only blocks denied domains so ask destinations can reach SOCKS5 approval.
- Replace `openclaw secrets reload` with direct WebSocket RPC via node. The openclaw CLI hangs in container environments (confirmed bug in openclaw 2026.4.5 where any subcommand hangs). The node script reads gateway config from disk, opens a WebSocket to 127.0.0.1, and sends the secrets.reload RPC directly. - Add retry with backoff for startup env injection. Sluice starts before openclaw (compose healthcheck ordering), so the first few docker exec attempts fail with "container not running". Retries at 0, 2, 5, 10, 30 second intervals. - Add --bypass 127.0.0.0/8 and ::1/128 to tun2proxy in all compose files so localhost traffic inside the openclaw container stays on loopback and doesn't get routed through the SOCKS5 proxy.
…ng, reload retry - Use SLUICE_PHANTOM:<credname> format for env var injection instead of GeneratePhantomToken() random hex. The MITM proxy only recognizes the SLUICE_PHANTOM: prefix for byte-level replacement in HTTP headers and body. Previously the env phantom and MITM phantom were different formats, so credential swap never worked for env-injected keys (e.g. GEMINI_API_KEY). - Add entrypoint wrapper in compose that sources ~/.openclaw/.env before starting openclaw so child processes (gemini --acp) inherit phantom tokens in their process environment. - Add ReloadSecrets method to ContainerManager interface. All backends (Docker, Apple, Tart) implement it using a WebSocket RPC script that sends secrets.reload directly to the gateway. This bypasses the openclaw CLI which is slow in container environments. - Add phase 2 retry loop for secrets reload after env injection. The gateway takes longer to start than the container, so the reload retries with backoff (5, 10, 20, 30, 60s) after env file is written. - Add NODE_COMPILE_CACHE and NPM_CONFIG_PREFIX env vars in compose for persistent Node.js compile cache and npm global installs.
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
SNI-based policy evaluation
Telegram approval UX
Container/credential injection
Infrastructure
Test plan