// Debug failures in the Cloudflare OS worker using the Cloudflare MCP server. Use when diagnosing 500s, missing logs, or request-level regressions in production or preview.
| name | debug-os-worker |
| description | Debug failures in the Cloudflare OS worker using the Cloudflare MCP server. Use when diagnosing 500s, missing logs, or request-level regressions in production or preview. |
| publish | false |
Debug production/preview issues in the Cloudflare worker deployed from apps/os.
apps/os/src/.os in preview/dev; confirm in Cloudflare dashboard).Use Cloudflare observability MCP tools with:
view: "events"Collect real values for trigger, message, error, requestId, level.
Filter on error level or distinctive message fragments from the alert.
Map failures to handlers under:
apps/os/src/entry.workerd.tsapps/os/src/orpc/apps/os/src/domains/apps/os and machine/daemon control-plane paths were removed from this repo.Create a new Cloudflare app in this repo with the expected package scripts, Doppler shape, and CI workflow wiring.
Query and analyze Cloudflare Workers traces through the general Cloudflare API MCP server. Use when diagnosing Workers traces, distributed tracing spans, observability events, subrequest chains, or when an agent needs Cloudflare trace data programmatically.
Debug MCP servers with the official MCP Inspector UI and CLI. Use when an MCP server will not connect, auth fails, tools/resources/prompts are missing, or a tool call needs to be reproduced outside Codex/Claude.
Drizzle ORM database migration workflow for packages that still use Drizzle (agents, example). Do NOT use for apps/os — that app uses sqlfu/D1.
Monitoring workflow for architect: Cloudflare Worker checks, task updates, and Slack escalation.
PostHog alert responder workflow with required Slack deep-links and escalation rules.