Skip to content

Add Workers development and debugging tool discovery - #185

Draft
irvinebroque wants to merge 3 commits into
mainfrom
codex/workers-verification
Draft

irvinebroque wants to merge 3 commits into
mainfrom
codex/workers-verification

Conversation

@irvinebroque

@irvinebroque irvinebroque commented Sep 5, 2026 •

Copy link
Copy Markdown
Collaborator

Agents need to know which Cloudflare development and debugging tools are available and how to discover their operations. Add workers-development, a concise capability map covering Wrangler and Cloudflare Vite development, Local Explorer data and telemetry APIs, production observability, and preview deployment discovery. Register it in the README and Cloudflare troubleshooting route.

Local guidance starts with the dev server's route hints and examples, extracting relevant OpenAPI operations when needed. It includes discovery when a hint is absent and a version/docs fallback when capabilities are missing. Production guidance routes through the bundled Cloudflare MCP server's search and execute tools to telemetry keys, values, and queries, including trace summaries. The optional Workers Observability MCP server and wrangler tail are alternative tools. Trace details and sampling remain discoverable through current schemas and docs.

Add a short preview section to Wrangler covering command and account eligibility, the project build workflow, version uploads, and resource sharing. A locally executing Worker can use remote bindings, and a preview URL does not establish storage isolation.

Validation:

  • Local smoke tests with Wrangler 4.129.0 and Cloudflare Vite plugin 1.54.4 / Vite 8.2.2, using a temporary Worker and local KV binding on nondefault ports.
  • Both dev servers printed usable Explorer discovery hints. Retrieved OpenAPI, seeded KV via its API, verified the Worker read the value, and queried captured binding spans and console logs. Repeated the Vite check after clearing the temporary telemetry store to distinguish its results.
  • A deliberate Vite handler exception returned HTTP 500 and was located in the trace's recorded HTTP status attribute. Its runtime outcome remained ok, so filtering only by an error column would have missed it.
  • Live MCP schema discovery confirmed telemetry keys/values/query operations and view: traces for distributed trace summaries. No production account data was queried.
  • Installed wrangler preview --help confirmed the command, naming options, and private-beta designation. No preview was deployed or account eligibility tested.
  • quick_validate.py passed for both changed skills; git diff --check passed. Temporary dev servers were stopped.

These are direct capability smoke tests and a documentation/schema review, not an independent agent benchmark. They establish that the documented discovery paths work in the tested versions; they do not establish production permissions, coverage of every binding type, or preview deployment success.

Documentation gap: cloudflare/cloudflare-docs#31775 remains open, while the published Preview URLs page describes version uploads. Preview guidance checks current docs, installed support, and beta eligibility instead of copying the proposed configuration and isolation matrix. Sources include the linked Local Explorer, Observability, Workers Traces, real-time logs, and version URL documentation, the MCP README/tool implementation, and the live MCP OpenAPI schema.

@irvinebroque irvinebroque changed the title Add Workers verification with local traces and Explorer Add Workers development and debugging tool discovery Sep 5, 2026
@irvinebroque
irvinebroque marked this pull request as draft September 8, 2026 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant