Topic
#debugging
Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.
Loot
More from this topic
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Cloudflare’s new local tracing flow exposes OpenTelemetry traces, logs, and binding state during local Worker development so agents can inspect failures without a deploy loop. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. Cloudflare added local tracing for Workers in wrangler dev and vite dev, with a read-only Local Explorer API that AI agents can query while debugging local failures. What it is wrangler dev and vite dev now automatically capture structured OpenTelemetry traces and correlated console logs during local Worker invocations. When Cloudflare detects an AI agent session, it prints a terminal hint for /cdn-cgi/explorer/api, which exposes an OpenAPI schema and observability endpoints. Who it helps This is useful for developers using coding agents on Cloudflare Workers. Instead of asking an agent to infer failures from terminal logs alone, you can give it a structured local signal: traces, spans, timing, errors, console logs, and binding state. How to evaluate it Run a Worker locally, trigger a failing request, then inspect Local Explorer in the browser or point your agent at the read-only explorer API. Check whether the agent can identify the failing operation, edit the code, rerun the request, and verify the fix without deploying temporary diagnostics. Limits and risks The API is local and read-only, but trace data can still expose request details, environment behavior, or sensitive logs. Review what your Worker logs before handing the endpoint to an agent. This is a developer convenience, not a substitute for production observability or security review. Sources Cloudflare changelog
Free
Review open
APXY gives developers and coding agents a local proxy for capturing HTTP traffic, replaying failures, mocking APIs, and exporting network evidence without guessing from logs alone. APXY is a local network debugging and API mocking proxy built for developers who now hand real debugging work to coding agents. It sits between an app and the network, captures HTTP/HTTPS requests, and exposes the evidence through a CLI plus a Web UI. The practical angle is simple: when an agent changes frontend code, auth handling, SDK calls, or mobile flows, APXY can give it concrete request and response data instead of a vague bug report. The official docs list traffic capture, filtering, mock rules, redirects, replay/export, API diagnosis, SSL proxying, network-condition simulation, and SQL-style queries over captured requests. Where it fits Use APXY when a bug depends on network behavior: a backend returns a different shape than expected, a mobile client fails behind HTTPS interception, a flaky API needs to be mocked, or an AI coding agent needs exact evidence before touching code. The project also publishes workflow examples for basic debugging, API mocking, and agent-assisted troubleshooting. The GitHub repository includes an agent skill path, examples, mock templates, docs, and install options via shell script or Homebrew. The public site lists a free tier with Web UI access, 200 traffic records, 3 active mock rules, core CLI commands, and 30-minute sessions. Paid one-time licenses unlock unlimited history and advanced controls. Caveats before use Treat it as a network-inspection tool, so review certificate handling, captured request storage, and team privacy expectations before using it on production traffic or customer data. The GitHub API currently reports no SPDX license for the repository, so do not assume open-source reuse rights beyond normal use of the distributed tool and published docs. For agent workflows, start with non-sensitive local or staging traffic. Install scripts should be reviewed before execution, especially in locked-down environments. If the tool fits your workflow, the biggest value is not another dashboard; it is giving your agent a reproducible network record it can inspect, mock, replay, and use to verify its own fix.
Free
Review open
Prism.Tools is a free GitHub Pages toolbox with client-side utilities for JSON, SQL, YAML, JWTs, hashes, regex, QR codes, CSS helpers, encoders, timestamps, diffs, and quick dev cleanup work. What it is Prism.Tools is a free browser-based toolbox for small developer chores that should not require a SaaS login. The official page positions it as a fast, private, free-forever collection where data stays in the browser, with visible categories for formatters and parsers, security/dev utilities, visual and CSS helpers, generators, content tools, encoders, and transformers. The practical value is simple: bookmark one page for the tasks that interrupt real work. Use it for formatting JSON or SQL, converting YAML and JSON, checking regexes, decoding JWTs, generating hashes or UUIDs, building QR codes, parsing URLs, previewing Markdown, sorting lists, converting timestamps, or producing quick CSS and SVG helpers. Why bookmark it Use Prism.Tools when you need a quick local-first utility but do not want to paste sensitive snippets into a random ad-supported formatter. It is especially useful beside AI coding agents: let the agent write the plan or code, then use a focused browser utility to inspect the exact token, payload, diff, timestamp, color, QR code, or serialized data you are about to ship. The HN launch thread describes the project as a set of standalone client-side HTML tools, hosted on GitHub Pages, with minimal external dependencies for specific utilities. Treat that thread as context, not documentation; the source you should actually use is the live tool page and your own browser/network inspection. Access and caveats The public page says the toolset is free and that data does not leave the browser. That makes it useful for low-risk and moderately sensitive cleanup tasks, but it is still a public website. For secrets, regulated data, customer exports, production JWTs, or proprietary source snippets, verify the Network panel first or use a self-hosted/offline tool you control. The GitHub repository link advertised by the live page was not reliably accessible through the public API during this check, so do not assume open-source review is available until you confirm the repository yourself. Also expect lighter UX and narrower coverage than larger tools such as CyberChef or IT Tools; Prism.Tools is best as a quick bookmark, not a full analysis suite. Quick fit check Need Prism.Tools fit Caveat --- --- --- Format or convert data JSON, SQL, YAML, URL, timestamp, string, and list helpers Verify behavior before touching production data Inspect auth/debug values JWT, hash, UUID, base64, URL parser, diff, regex tools Do not paste live secrets without network checks Create small assets QR, favicon, CSS gradient/shadow/grid, SVG helpers Not a full design system Keep agent work grounded Use focused tools to inspect generated payloads HN prompt examples were not reused Sources checked Primary source: the live Prism.Tools page on GitHub Pages. Secondary source: the public Show HN launch discussion, used only to corroborate intended use, launch context, and caveats. External comments and prompt examples were treated as untrusted source text and not copied into this Loot.
Free
Review open
Blog