Run any Skill in Manus with one click

gateway-proxy-debug

Stars116

Forks32

UpdatedMay 8, 2026 at 16:45

Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Use when the OpenClaw UI, WebSockets, gateway proxying, or waiting-page flow breaks.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

vercel-labs

vercel-labs/vercel-openclaw

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	gateway-proxy-debug
description	Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Use when the OpenClaw UI, WebSockets, gateway proxying, or waiting-page flow breaks.

Gateway Proxy Debug

Use this skill when the wrapper can reach a sandbox but /gateway, HTML injection, WebSockets, or token handoff is broken.

Evidence First

Collect:

Browser URL and failing request path.
GET /api/status.
GET /api/admin/sandbox-diag.
GET /api/admin/logs filtered for proxy., gateway., sandbox.port_, token..
Network trace for /gateway/*, WebSocket upgrade, and POST /api/status heartbeat.

Keep app auth, deployment protection bypass, gateway token, and AI Gateway auth separate. Do not paste gateway tokens in artifacts.

Path Diagram

browser -> wrapper auth -> /gateway route -> ensure sandbox running
  -> fresh gateway token -> sandbox port URL -> OpenClaw gateway
  -> HTML injection -> WebSocket rewrite -> heartbeat POST /api/status

Mark each edge unknown, verified-good, or verified-bad.

Common Failure Splits

Waiting page is correct because sandbox is not ready yet.
Proxy auth failed before any sandbox request.
Cached port URL is stale and needs invalidation.
Gateway token is stale or not injected.
HTML injection failed or produced a malformed script.
WebSocket URL rewrite points at the wrong origin/path.
Heartbeat is missing and sandbox times out.

Fix Boundaries

Primary: src/app/gateway/[[...path]]/route.ts.
Helpers: src/server/proxy/{proxy-route-utils,htmlInjection,waitingPage}.ts.
Lifecycle dependencies: src/server/sandbox/lifecycle.ts, src/server/public-url.ts.
Tests: proxy/html injection tests plus lifecycle tests for heartbeat interactions.
Docs: lat.md/sandbox-lifecycle.md, docs/architecture.md, docs/deployment-protection.md.

Verification

Run focused tests when available, then:

node scripts/verify.mjs --steps=test,typecheck
lat check

For UI/WebSocket fixes, verify in a browser or with a smoke check that HTML contains the injected script and WebSocket traffic reaches the sandbox.

More from this repository

same repository

sandbox-lifecycle-debug

vercel-labs/vercel-openclaw

Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks. Use when sandbox state transitions, status polling, stop/resume, reset, or lifecycle recovery is wrong.

2026-05-09116

sandbox-v2-lifecycle

vercel-labs/vercel-openclaw

Vercel Sandbox v2 lifecycle expertise for vercel-openclaw: named persistent OpenClaw sandbox create/resume/stop/delete, persistent auto-save truth, manual snapshot diagnostics, short-lived worker sandboxes, hot spares, and SDK v2 semantics.

2026-05-09116

admin-ui-debug

vercel-labs/vercel-openclaw

Admin UI and operator surface debugging for vercel-openclaw: command shell design, admin actions, request core, status panels, launch verification UI, channel readiness UI, and local read-only production-data workflows. Use when the root admin UI, controls, visual state, or operator copy is wrong.

2026-05-08116

auth-store-debug

vercel-labs/vercel-openclaw

Auth and store debugging for vercel-openclaw: admin-secret mode, Sign in with Vercel, session cookies, CSRF, LOCAL_READ_ONLY, Redis vs memory store, keyspace namespacing, and metadata shape migrations. Use when login, route authorization, Redis persistence, or metadata state is suspect.

2026-05-08116

cron-watchdog-debug

vercel-labs/vercel-openclaw

Cron and watchdog debugging for vercel-openclaw: Vercel Cron auth, persisted OpenClaw jobs, cron wake keys, token refresh, restore oracle, hot spare, and watchdog reports. Use when scheduled OpenClaw jobs fail to wake or run, watchdog status is wrong, cron persistence is suspect, or /api/cron/watchdog behavior changes.

2026-05-08116

firewall-ai-gateway-debug

vercel-labs/vercel-openclaw

Firewall and Vercel AI Gateway debugging for vercel-openclaw: network policy allowlists, OIDC token refresh, AI Gateway transform rules, firewall learning/enforcement, and sandbox.update networkPolicy calls. Use when model calls, egress, token refresh, or firewall policy application fails.

2026-05-08116

name	gateway-proxy-debug
description	Gateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Use when the OpenClaw UI, WebSockets, gateway proxying, or waiting-page flow breaks.

Gateway Proxy Debug

Use this skill when the wrapper can reach a sandbox but /gateway, HTML injection, WebSockets, or token handoff is broken.

Evidence First

Collect:

Browser URL and failing request path.
GET /api/status.
GET /api/admin/sandbox-diag.
GET /api/admin/logs filtered for proxy., gateway., sandbox.port_, token..
Network trace for /gateway/*, WebSocket upgrade, and POST /api/status heartbeat.

Keep app auth, deployment protection bypass, gateway token, and AI Gateway auth separate. Do not paste gateway tokens in artifacts.

Path Diagram

browser -> wrapper auth -> /gateway route -> ensure sandbox running
  -> fresh gateway token -> sandbox port URL -> OpenClaw gateway
  -> HTML injection -> WebSocket rewrite -> heartbeat POST /api/status

Mark each edge unknown, verified-good, or verified-bad.

Common Failure Splits

Waiting page is correct because sandbox is not ready yet.
Proxy auth failed before any sandbox request.
Cached port URL is stale and needs invalidation.
Gateway token is stale or not injected.
HTML injection failed or produced a malformed script.
WebSocket URL rewrite points at the wrong origin/path.
Heartbeat is missing and sandbox times out.

Fix Boundaries

Primary: src/app/gateway/[[...path]]/route.ts.
Helpers: src/server/proxy/{proxy-route-utils,htmlInjection,waitingPage}.ts.
Lifecycle dependencies: src/server/sandbox/lifecycle.ts, src/server/public-url.ts.
Tests: proxy/html injection tests plus lifecycle tests for heartbeat interactions.
Docs: lat.md/sandbox-lifecycle.md, docs/architecture.md, docs/deployment-protection.md.

Verification

Run focused tests when available, then:

node scripts/verify.mjs --steps=test,typecheck
lat check

For UI/WebSocket fixes, verify in a browser or with a smoke check that HTML contains the injected script and WebSocket traffic reaches the sandbox.