worker-logs_skill

Overview

This skill tails and inspects Cloudflare Worker logs from the CLI to help debug the site and API Workers. It focuses on real-time request/response traces, console output, and authentication diagnostics for the homepage worker (apps/web) and the API worker (apps/api). Use it to see why requests return 401/500 and to verify headers, secrets, and runtime errors.

How this skill works

Run wrangler tail from the worker’s app directory (or pass --config/--cwd) to open a live streaming log of requests, statuses, and console output. You can filter the stream (status, method, header, search text, JSON vs pretty) and run separate tails for the web and API workers in parallel. Logs are real-time only; for historical data use the Cloudflare dashboard or Logpush.

When to use it

• Reproducing 401/500 errors from openagents.com or openagents.com/api.
• Verifying that X-OA-Internal-Key or other headers arrive intact and why authorization failed.
• Watching console.log and console_error output from the Rust API or the web app while reproducing an issue.
• Correlating Convex or other service calls with API worker behavior by tailing both sides simultaneously.
• Monitoring live traffic during deployments or troubleshooting intermittent failures.

Best practices

• Run npx wrangler tail from the worker’s app directory (apps/api or apps/web) or pass --config/--cwd to point to the correct wrangler file.
• Use --format json when piping into tools like jq for reliable filtering and correlation with other logs.
• Filter aggressively (--status, --method, --search, --header) to reduce noise and avoid sampling on high traffic.
• Set --sampling-rate 1 to capture 100% of requests if you suspect sampling hides the issue.
• Do not log secrets directly; log presence/length or masked values for diagnostics.

Example use cases

• Debug a 401 from the API: cd apps/api && npx wrangler tail --status error while reproducing the failing request to see openclaw auth lines.
• Trace a page error: cd apps/web && npx wrangler tail and reproduce the UI flow to capture console logs and request statuses.
• Compare Convex and API activity: Terminal 1 tails apps/api, Terminal 2 tails apps/web, Terminal 3 shows Convex logs; reproduce the flow to follow the request chain.
• Filter logs for openclaw: npx wrangler tail --format json | jq 'select(.url|contains("openclaw"))' to inspect only relevant API calls.