Worker Logs

What it does

This skill allows an AI agent to access and display real-time logs from Cloudflare Workers, specifically those used by openagents.com and its API. It provides visibility into request paths, response statuses, console output, and errors generated by these workers. This is useful for debugging issues and understanding the behavior of the deployed Workers.

When to use it

• Debugging HTTP 401 or 500 errors originating from openagents.com or openagents.com/api.
• Verifying that a Worker receives expected headers (like X-OA-Internal-Key) and identifying why an "unauthorized" response might be returned.
• Viewing console log output from the Rust API or web application.
• Correlating logs with Khala logs when troubleshooting interactions between Khala and the API worker.
• Monitoring request flow across both the main site and the API for comprehensive debugging.

Key capabilities

• Accesses real-time Cloudflare Worker logs.
• Supports viewing logs from two specific Workers: openagents-api (Rust API) and openagents-web-app (main website).
• Provides options to filter logs by status (ok, error), HTTP method, URL path, header presence, or search terms within console output.
• Supports both human-readable ("pretty") and JSON formatted log outputs.
• Allows for 100% request logging via --sampling-rate 1.

Example prompts

• "Show me the error logs from the API worker."
• "Display all requests to the web app worker with a status code of 500."
• "Filter the API worker logs for messages containing 'legacyparity'."

Tips & gotchas

• This skill provides real-time log streaming only. Historical data requires using the Cloudflare dashboard (Workers & Pages -> your worker -> Logs / Real-time Logs or Logpush).
• To view logs from both workers, run wrangler tail in separate terminals within the apps/api and apps/web directories.
• The default sampling rate may not log every request; use --sampling-rate 1 to ensure all requests are logged.