All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Security
Security
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Workers - Local Explorer for local resource data

2mo ago

Source

CloudflareWorkers - Local Explorer for local resource datacloudflare.com
Snippet from the RSS feed
Local Explorer is a browser-based interface and REST API for viewing and editing local resource data during development. It removes the need to write throwaway scripts or dig through .wrangler/state to understand what data your Worker has stored locally. Local Explorer is available in Wrangler 4.82.1+ and the Cloudflare Vite plugin 1.32.0+. Start a local development session and press e in your terminal, or navigate to /cdn-cgi/explorer on your local dev server. Supported resources Local Explorer supports five resource types and works across multiple workers running locally: KV — Browse keys, view values and metadata, create, update, and delete key-value pairs. R2 — List objects, view metadata, upload files, and delete objects. Supports directory views and multi-select. D1 — Browse tables and rows, run arbitrary SQL queries, and edit schemas in a full data studio. Durable Objects (SQLite storage) — Browse individual object SQLite tables, run SQL queries, and edit schemas. Workflows — List instances, view status and step history, trigger new runs, and pause, resume, restart, or terminate instances. OpenAPI-powered REST API Local Explorer exposes a REST API at /cdn-cgi/explorer/api that provides programmatic access to the same operations available in the browser. The root endpoint returns an OpenAPI specification describing all available endpoints, parameters, and response formats. curl Point an AI coding agent at /cdn-cgi/explorer/api and it can discover and interact with your local resources without manual setup. This enables iterative development loops where an agent can populate test data in KV or D1, inspect Durable Object state, trigger Workflow runs, or upload files to R2. For more details, refer to the Local Explorer documentation .

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.