Ephemeris.
Every pick today hands an agent something it could not see yesterday: the rule that blocks a merge, the trace already sitting on your laptop, the comment that starts a job, the config that governs ten thousand repositories. Two of them arrive with real numbers attached, which is rarer than it should be for this kind of announcement. The other three are small enough to try before lunch.
The editor · 08:00 CEST
Your standards are prose. The reviewer needs JSON.
Cloudflare writes its engineering standards as RFCs — anyone can open one, it takes rounds of review, a domain owner signs off. The part worth stealing is what happens next: the prose is compiled into JSON statements tagged MUST or SHOULD, each with a stable slug, so a review agent pulls the four rules that apply to a diff instead of dragging the whole corpus through its context window.
The trace is on your laptop before you deploy
Update Wrangler and wrangler dev starts emitting OpenTelemetry spans for fetches, handler lifecycles and every binding call — KV, R2, D1, Durable Objects, Queues — captured by workerd itself. The dev server notices when a coding agent is attached and prints a query endpoint, so the agent reads the failing span and the correlated console logs instead of asking you to paste them.
$ wrangler dev
→ Local Explorer API ready
POST /cdn-cgi/explorer/api/local/observability/query
SQL over traces + correlated logs
vite dev with @cloudflare/vite-plugin@latest.Leave a comment. The agent picks it up.
Copilot cloud agent automations can now fire on an issue or pull-request comment, matching text you choose. The trigger is the cheap part — what it buys is a place to park the jobs nobody schedules: regenerate the docs a diff invalidated, go read the error log attached to a bug, open the refactor ticket someone promised to file.
Repository → Agents → Automations
On Copilot Pro, Pro+, Max, Business and Enterprise. Business and Enterprise need an administrator to switch on the cloud agent policy first.
One config file, every repository you own
CodeQL default setup was the version you took when you did not want to maintain a workflow file in every repository. A new repository property, github-codeql-config-file, points default setup at a config of yours and merges it with the built-in one — extra queries, excluded paths, a chosen threat model — set as an organisation-wide default and overridden per repo where it matters.
value .github/codeql-hardened.yml
scope org default · per-repo override
source may live in another repo · private via Git Source registry
merge your queries + defaults, threat models preserved
status GA on github.com · ships in GHES 3.23
A billion requests a month, and nobody on infrastructure
Factory runs its entire cloud backend as one Next.js application: customer-facing API routes, auth and routing middleware, webhook handlers, log-drain pipelines. No separate services, no platform team, observability and WAF taken from the platform rather than assembled.
“Infrastructure has never slowed us down.”Nikita Lilichenko · Factory
That's today.
Issue 106, 5 August 2026. Five picks from three sources, read this morning in Zürich across four newsletters, seven engineering blogs, two model labs and five Telegram channels.
Read today
The Batch · Don't Worry About the Vase · Import AI · Jeff Bullas. OpenAI · Anthropic. GitHub · Sentry · Vercel · PostHog · Cloudflare · Fly.io · Next.js. @seeallochnaya · @TochkiNadAI · @denissexy · @rvnikita_blog · @ProductsAndStartups.
Rubric
AI tools you could adopt this week. Creative software and generative media. Dev tools and agentic coding. Privacy and security when the signal is high. Research with a practical kernel. Anything immediately useful to a senior engineer or a founder.
House rules
Everything here was published within the last thirty days. Nothing here has run in a previous issue — every link is checked against the archive before it ships. Three to five stories, never more; a thin day gets a shorter issue rather than a padded one.