My PHP API Returned no-store and Cloudflare Passed Everything Through: Overriding Only the Edge TTL
The list API behind my wallpaper apps returned no-store, so putting Cloudflare in front of it changed nothing: every request still reached the origin. This note covers a Cache Rule that overrides only the edge TTL, a small script that proves it works, and a deploy step that pairs upload and purge so stale responses don't linger.
I Swapped an Immutable Asset at the Same URL, and Only the Browser Kept the Old Copy
Overwrite a long-cached JS file at the same URL and neither a CDN purge nor a refresh will make the browser fetch it again. Four delivery styles — same URL, no-cache, query string, content-hash filename — compared in Chromium, plus a complete build-step script that adds the hash.
Purging Cloudflare Didn't Bring Back the New Wallpapers: the Stale JPEGs Were Held by XPageSpeed on the Origin
An operations record from a wallpaper app: images overwritten at the same URL kept arriving stale even after a Cloudflare purge. Covers the three-way local/origin/edge probe that names the guilty layer, when prefix purge beats per-URL purge, and how to switch off Xserver's XPageSpeed in .htaccess without a 500.
Stateful AI Agents on Antigravity × Cloudflare Durable Objects — One Session, One Instance, One Place to Manage Conversation, Tools, and Cost
How to deploy an Antigravity AgentKit 2.0 agent onto Cloudflare Durable Objects so that conversation history, tool-call state, and token spend live inside a single instance per session — with the actual code and production cost numbers from my own deployment.
Antigravity × Cloudflare Vectorize: Build a Production RAG Pipeline That Runs at the Edge
A production guide to building a RAG pipeline on Cloudflare Vectorize using Antigravity. Chunking, hybrid search, cost design, and observability—covered at a depth a solo developer can actually ship.
Antigravity × Cloudflare Edge SaaS Architecture Guide: Production Patterns with D1, Workers, R2, and Workers AI
A complete production guide for building edge SaaS with Antigravity + Cloudflare D1, Workers, R2, and Workers AI. Covers real pitfalls including N+1 queries, CPU limits, and cost management.
When the Edge Cache Pinned Next.js Error Pages: A cache-worker Guard Design
Users reported intermittent 'failed to load' errors I could never reproduce. The cause: SSR exceptions shipped as HTTP 200 and pinned by the edge cache. Here is how I narrowed it down with an Antigravity agent and added a cache-worker guard to stop it.
Rebuilding Wallpaper Image Delivery Around Resolution Buckets — Letting an Antigravity Agent Own Conversion and Validation
Every new device resolution quietly makes a wallpaper app heavier. I stopped shipping one master image to every device and rebuilt delivery around resolution buckets, WebP/AVIF, and an edge redirect — then handed conversion and validation to an Antigravity agent. Real code and thresholds included.
CORS Errors Blocking API Tests in Antigravity — How to Diagnose and Fix by Environment
Fix CORS errors that block API testing in Antigravity development. Learn how to identify the root cause by environment — Next.js, Cloudflare Workers, Supabase — and craft precise prompts so Antigravity generates the right fix.
Build a File Upload & Image Optimization Pipeline with Antigravity and Cloudflare R2
Learn how to build a complete file upload system with image optimization using Antigravity's AI agents and Cloudflare R2 — with presigned URLs, automatic WebP conversion, and production-ready error handling.
Next.js × Antigravity Web Dev Guide — AI-Driven Full-Stack Development
Learn how to leverage Antigravity with Next.js for efficient full-stack development from project setup to deployment.