Cloudflare
Which Workers actually run in production, mapped back to your code.
Neat pulls Workers invocation telemetry from the Workers Observability API and maps each invocation back to the code path that serves it.
Paste it into your coding agent — it runs the full setup with your credentials.
Set up NEAT's Cloudflare connector so you can see which Workers actually run in production. It pulls WORKERS INVOCATION TELEMETRY (the Workers Observability query API). Steps:
1. Ensure NEAT is running for this repo.
2. Gather my Cloudflare ACCOUNT ID (dash.cloudflare.com account home) and an ACCOUNT-SCOPED API TOKEN with Workers Observability read (create at dash.cloudflare.com/profile/api-tokens; export as CF_TOKEN, don't paste inline). The token MUST be account-scoped — a user-scoped token fails validation. For each Worker to map, note its SCRIPT NAME, the SERVICE in my graph it belongs to, and its ENTRY FILE (e.g. src/index.ts).
3. Run: npx neat.is connector add cloudflare --account-id <id> --token $CF_TOKEN
Then add the workers map to this entry's options.workers in ~/.neat/connectors.json: { "<script>": { "service": "<svc>", "entryFile": "<path>" } } — or answer the interactive prompts.
4. Restart the daemon to begin polling.
5. Verify: hit the Workers to generate invocations, then check the graph for OBSERVED CALLS edges from each service onto its Worker. Report which Workers show real traffic. how it works
See which Workers actually run in production — and which declared ones never fire.
- Gather your account ID and an account-scoped API token with Workers Observability read, plus each Worker's script name, service, and entry file.
- Run the connector, add the workers map, and restart the daemon to begin polling.
- Hit the Workers — OBSERVED CALLS edges appear from each service onto its Worker.
