cloudflare-operations

name	cloudflare-operations
description	Cloudflare Workers runtime debugging for services in email/, workers/, and agent/. Use wrangler tail for live log stream and Cloudflare Dashboard for past invocations. Deployment is automated via GitHub Actions. Use when debugging email-worker, paste, email-agent, or any Cloudflare Worker in this repository.
context	fork
keywords	cloudflare, wrangler, workers, email-worker, paste, email-agent, email-routing, wrangler-tail, cloudflare-dashboard, クラウドフレア

• Deployment is automated via .github/workflows/20_email.yaml / 20_workers.yaml / 20_agent.yaml — do NOT run wrangler deploy manually
• Use npx wrangler tail <worker-name> --format pretty for live log stream
• For past invocations, open Cloudflare Dashboard → Workers & Pages → → Logs

Services

Path	Worker Name	Trigger	Bindings
email/	email-worker	Email Routing (*@kaidotio.dev)	AI, SEND_EMAIL
workers/	paste	HTTPS requests	ASSETS, PASTE_KV, PASTE_BUCKET
agent/	email-agent	Email Routing ([e-mail]) + Slack webhook (agent.kaidotio.dev/slack/interactive)	AI, EMAIL, EmailAgent DO

Debugging

Symptom	Action
Runtime error / panic	npx wrangler tail <worker-name> --format pretty, then reproduce
Historic invocation inspection	Dashboard → Workers & Pages → → Logs
Local reproduction	npm run dev from email/, workers/, or agent/

Live Log Tail

Tails stream only future events; use Dashboard Logs for history.

cd email && npx wrangler tail email-worker --format pretty
cd workers && npx wrangler tail paste --format pretty
cd agent && npx wrangler tail email-agent --format pretty

Reference

If writing Next.js-on-Workers code: See .claude/rules/workers.md