Loading…
Latest reads
Every post, summarised
Grounded summaries of engineering blogs, newest first. Each links to the original.
- 4,738 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Latest posts
Detect and send production issues straight to your agent
Cloudflare introduces Issues, a built-in error monitoring feature for the Workers platform now in open beta. It automatically groups repeated exceptions, HTTP 5xx responses, and error logs into a single issue, eliminating manual telemetry linking. Developers enable it by setting observability.issues.enabled to true in wrangler.jsonc, with no SDK required. Issues captures stack traces, console logs, distributed traces, and Worker version, and via automations sends failure context—including user-provided identifiers—directly to a configured coding agent like Claude Code, Cursor, or Devin. The agent receives a structured summary and can further query logs through the Cloudflare MCP to propose code changes and open a pull request. Internally, the Workflows team uncovered and fixed two production bugs within a day using Issues (a migration retry loop and an incomplete deletion process).
Simplifying domains for people and agents
Cloudflare Registrar introduced a redesigned domain search that shows every supported extension and responds progressively as the user types. The search gathers availability evidence from prepared datasets, DNS, and live registry checks, updating only changed results via WebSocket deltas. The system uses Workers, Durable Objects, and Workers KV on Cloudflare’s developer platform to coordinate more than 420 extension checks per query. The Registrar API beta now includes a sandbox for testing, transfer support, and an extensions endpoint with registry requirements. Agents can search, register, or transfer domains through the MCP or the newly launched cf CLI with natural-language prompts.
Monetization Gateway beta: charge AI agents for consumption with HTTP 402
Cloudflare announced the Monetization Gateway closed beta, enabling domain owners to charge AI agents per request for websites, APIs, MCP tools, or datasets. The gateway uses the HTTP 402 Payment Required status code to allow inline payment without redirects or separate payment APIs. Sellers define pricing rules matching request parts and choose from several schemes, with settlement on the Base blockchain using USDC via Coinbase’s x402 Facilitator. Customer use cases include Cloudflare AI Gateway for inference, Ceramic.ai for web search, Stocktwits for stock signals, and API2PDF for document conversion. The beta is available to eligible U.S.-based sellers and buyers, with plans to support additional geographies and payment rails over time.
Pay Per Use: when AI uses your work, you should get paid
AI answer engines can read a publisher’s page and deliver a summary without the reader ever visiting the site, costing the publisher the visit and its associated revenue. Most publishers cannot negotiate individual licensing deals, and no AI company can contract with millions of sites. Pay Per Use, now in beta, is Cloudflare’s system that lets a buyer define a specific use of content and a price, and lets each publisher choose whether to accept that offer. The buyer reports each downstream use through a single Cloudflare API endpoint, and Cloudflare then bills the buyer and pays the publisher monthly. Publishers can track estimated earnings and usage by buyer and domain in the Cloudflare dashboard, with planned future enhancements such as report context like keywords or product type.
Identify AI model overuse with User Insights
Cloudflare AI Gateway’s User Insights now provides context beyond model names and request counts, using a dedicated Worker to classify conversations by task type such as coding, research, summarization, or formatting. The “model overkill” view identifies conversations where a high-capability reasoning model is used for simple tasks, showing which users or agents are driving that usage and the associated cost. Teams can analyze conversation turns to see how many back-and-forth exchanges a task requires, helping uncover inefficiencies in prompts or workflows. The Potential Savings view and Auto Router (closed beta) use task and model-fit signals to automatically route requests to appropriate models without a separate rule for each workload. These features are free for AI Gateway users and require stable user_id and session_id for analysis, with optional Access integration.
Cloudflare Containers, rebuilt to scale agent sandboxes
Cloudflare Containers have been rebuilt to meet the needs of agent sandboxes, which require on-demand creation, fast startup, and the ability to pause and resume. The new durable_object scheduling policy lets application code choose each sandbox’s image and instance type at runtime, replacing the previous deploy-time configuration. A redesigned runtime reduces median container startup from over four seconds to 648 milliseconds, and filesystem snapshots are available in public beta for saving and restoring workspaces. Each container retains its Durable Object as a persistent, programmable controller that manages its lifecycle and outbound traffic. These changes make Containers a more flexible complement to Workers and Durable Objects for agents needing a full Linux workspace.
The Internet has a second audience
More than half of Internet traffic is now automated, and AI agents are the fastest-growing part of it, with daily requests on Cloudflare’s network growing by more than 1,700% over the past year. This second audience consumes bandwidth without generating ad impressions or subscriptions, causing revenue per request to fall while costs rise. Cloudflare is giving site owners tools to see who is visiting, set terms per bot type, and charge for access. These include AI Crawl Control, Web Bot Auth for cryptographically verified agents, Disallow AI Training to block training without losing search indexing, and Pay Per Use to pay publishers when content is actually used. The goal is to build open standards so any site can set its terms and get paid, rather than a few companies controlling discovery and payment.
The Companions to Come
JetBrains is extending Kotlin’s companion mechanism with experimental companion blocks and companion extensions in Kotlin 2.5.0. Companion blocks replace the object keyword with a companion block, compiling members as static members on the JVM. Companion extensions allow adding class-level members to any type, even types the developer does not control. These features improve multiplatform interoperability by enabling expected companion block members to be actualized using Java static members. Companion objects remain fully supported and are still required when the companion must implement an interface, but companion blocks are recommended for new code.
How Etsy gets its mobile apps ready for peak traffic
Mobile apps cannot be reverted after release, so Etsy’s peak traffic preparation focuses on observability and mitigation decisions made months in advance rather than capacity scaling during the event. The company runs a code slush with three phases: mindful merging in mid-October, infrastructure fortification, and peak requiring senior sign-off for any change. To avoid tooling disruption, Etsy ran both legacy and new crash reporters simultaneously through a dual-reporting layer, letting engineers use the tool they knew and providing comparison data to eventually sunset the old platform. Before peak, each crash-prone feature is ensured to have a remote flag that disables the failing code path without an app store release. Crash rate is translated into an estimate of lost orders via business analysts, making technical health discussable with teams and the CTO.
Augment Voice Calls with Twilio Conversation Intelligence Using Node.js
Twilio Conversation Intelligence, Conversation Orchestrator, and Conversation Memory together analyze voice calls for a Node.js voice agent built with Conversation Relay. After a call, Twilio sends a webhook to /intelligence-results containing a call summary, sentiment analysis, and script adherence for categories like introduction with the required phrase “Thanks for calling Owl Air! I’m Hoot.” The developer creates a Memory Store and Conversation Configuration, then an Intelligence rule selecting Sentiment, Summary, and Script-Adherence operators triggered at conversation end. A Node.js handler extracts the data and persists it to a SQLite database using tables for intelligence_results, operators, and operator_script_adherence_categories. Testing involves calling the Twilio number and verifying the summary, sentiment, and script adherence records in the database.
Stripe’s Payment Method Factory: Orchestrating agents for repeated, custom integrations
Stripe offers over 125 different payment methods globally, each requiring integrations that previously took up to six months because teams started from scratch. They hypothesized that reusable prompts with hardening could reduce effort, and a bake-off showed vanilla Claude Code took 20 days versus 4 days with their prompts. The resulting factory has created three new payment method integrations and migrated ten existing ones to a modern stack, reducing timelines from six months to two to six weeks. The factory also uses code-based orchestration, continuous knowledge loops where agents suggest prompt improvements, and agents testing their own code against sandbox environments. The factory’s approach has since been extended to Stripe’s tax and verification teams for building their own connectors.
Seven Architectural Readiness Checks Before Production Launch
Auth0’s free tier supports up to 25,000 MAUs for MVPs, but teams must complete seven architecture checks before production launch to avoid blockers. The checks cover Auth0 Organizations for multi-tenancy, Enterprise Connections for SSO, Custom Domains, JIT hash migration, Fine-Grained Authorization, MFA factor progression, and tenant lifecycle management. The free plan caps Organizations at five, Enterprise Connections at one plus unlimited Okta, and MFA at passwordless and passkeys only. Upgrading to B2B Essentials or Professional unlocks unlimited organizations, up to five enterprise connections, and advanced MFA including TOTP, WebAuthn, push, and SMS; Professional also enables Custom Database migration scripts. Teams must add a credit card for Custom Domains, add a secondary admin to prevent tenant deletion after 150 days of inactivity, and note that FGA free trial supports 100 MAUs and 50,000 tuples for prototyping.
On the Effectiveness-Fluency Trade-Off in LLM Conditioning: A Systematic Study
Controlling the output of Large Language Models (LLMs) is a central challenge for their reliable deployment, yet current conditioning methods are often evaluated narrowly on effectiveness without considering generation quality. This study systematically investigates a range of conditioning methods in both concept injection and removal scenarios, including efficient steering, activation steering, prompting, and supervised fine-tuning. The authors find that efficient steering methods frequently achieve their conditioning goal at a steep cost to fluency, degrading generation quality. They identify a critical previously overlooked interaction: activation steering methods are far less effective on instruction-tuned models than on their base counterparts. Simple prompting and supervised fine-tuning are viable options for concept injection but are not as good at concept removal, while cheaply computed textual metrics highly correlate with costly LLM-as-judge scores, providing practical insights for evaluation.
How Atlas Agent Engine Powers MongoDB’s Internal AI Strategy
MongoDB announced the public preview of Atlas Agent Engine, a secure platform for building, deploying, and governing AI agents with built-in memory, retrieval, and open flexibility to choose any LLM or framework. The company validated the platform internally with Holly, a unified agentic workspace that replaces seven disconnected tools for sales reps and is powered by Atlas Agent Engine’s runtime, orchestration, and governance. Compared to manually hopping between tools, Holly cuts the time to research and build an outbound prospecting list by roughly 95%, reducing account prep from hours to minutes. Atlas Agent Engine enforces centralized controls and governance while granting developer autonomy, addressing CIO fears about agents running amok in enterprise systems. It is part of a trio of launches alongside MongoDB 9.0 and Atlas Infinite, giving builders a governed platform to run agents grounded in real-time operational data.
AI Demand is Constant, Unpredictable, and Extreme. MongoDB is Built for It.
AI-driven demand is constant, unpredictable, and extreme, unlike earlier internet and cloud eras where spikes were more predictable. Enterprises need a data layer that can absorb sudden bursts of traffic without re-architecture. MongoDB announced Atlas Infinite, a new deployment option within MongoDB Atlas that independently scales compute and storage within minutes. Atlas Infinite supports replica sets with 10x the data capacity of Atlas Core and delivers 189% more throughput per dollar in internal tests. MongoDB 9.0 was also released, offering up to 35% faster find-one queries and new security features like queryable encryption with prefix, suffix, and substring searches.
Building the Agentic Ecosystem: Partner Updates from MongoDB.local NYC
At MongoDB.local NYC, MongoDB launched Atlas Agent Engine in Public Preview, providing a single foundation for building, deploying, and governing AI agents. Six global systems integrators—Accenture, Capgemini, Cognizant, Infosys, TCS, and Tech Mahindra—are launch partners, integrating the engine into their AI offerings. The platform is model- and framework-neutral, with partners like Arize AI offering trace monitoring for production reliability. MongoDB also announced Devin for MongoDB Modernizations, leveraging Cognition’s AI software engineer to automate legacy code migration while AMP handles data movement. New partnerships with Emergent, Monk.io, and Retool extend MongoDB’s reach into AI application development and internal tools, reinforcing that the agentic era requires an ecosystem of partners with industry expertise.
Context Engineering Has a Retrieval Issue: Introducing rerank-3 and Native Reranking
AI agents require precise context retrieval, not larger windows, and MongoDB’s new Rerank-3 and Rerank-3-lite models outperform Cohere Rerank v4.0 Pro by 2.14% and Qwen3-Reranker-8B by 3.31% overall, with greatest improvements on long documents and code. The $rerank native aggregation stage rescores candidate sets index-free within MongoDB, while Automated Embedding generates and refreshes vectors near-real-time to prevent model version drift. This unified platform eliminates separate vendors and external API calls, supporting lexical, vector, and hybrid search directly against operational data without moving or syncing. The result is simpler retrieval architecture that improved Gravity’s accuracy and cut latency by roughly 50% by better discriminating between strong and weak matches. Retrieval quality forms one layer of MongoDB’s broader agent platform, which also includes performance scaling with Atlas Infinite and agent memory with Atlas Agent Engine.
Open TTS Leaderboard: Scalable Evaluation for Multilingual Text-to-Speech and Voice Cloning
The open-source TTS model landscape has exploded, with over 8,000 models on Hugging Face Hub, yet evaluation methods remain unstandardized and cannot scale. The Open TTS Leaderboard addresses this by using objective metrics such as word error rate (WER), speaker similarity (SIM), and speed (RTFx and TTFA) to evaluate models in hours instead of weeks. It supports multilingual evaluation and voice cloning, providing separate tabs for listening to outputs and comparing streaming performance. Unlike arena-based leaderboards that significantly underrepresent open models due to high hosting costs, this leaderboard prioritizes open-source models. The project encourages community participation through feedback and voting; evaluation scripts will be open-sourced soon, and future updates will incorporate new datasets, languages, and metrics.
Warmup Services Harm Your Deliverability
Warmup services that simulate email engagement harm deliverability because inbox providers detect the pattern and tighten filtering, causing reputation decline that makes recovery harder. Validity’s new Heatwave blocklist identifies domains warmed through synthetic engagement, using signals from its Intelligence Network to automatically list domains crossing a threshold, and over 1.2 million domains have already been listed. The signal is shared with providers including Comcast, Proofpoint, Spamhaus, and SURBL, potentially damaging domain reputation with these providers. A domain on Heatwave receives a permanent record, and even if the domain stops cold outreach, the warming listing stays, making recovery difficult or impossible. Legitimate senders should verify their domain at lookup.validity.tools, obtain proper consent, and increase volume gradually through real engagement, as the domain warms itself through real engagement and there is no shortcut to trust; warmup activity may also run through agencies without the sender’s knowledge.
How Notion built a Custom Agent workflow to keep Academy content current
Notion built a Custom Agent workflow in Notion to keep Academy content current as product changes ship. The system uses two databases: an Academy library mapping the curriculum and a maintenance-tasks database tracking work from each product change. Two Custom Agents handle the work: the Academy Drift Agent compares launch docs against the library and flags affected lessons, while the Academy Drafting Agent drafts approved updates using editorial guidance. MCP connects the workflow to Parta, the e-learning platform, so approved content moves into final QA without manual hand-off. The loop includes human review checkpoints before scope approval and before content moves into Parta, reducing content drift and giving the team hours back each week.
Top topics
- Architecture834
- Performance817
- LLMs673
- Machine Learning622
- Open Source568
- AI Agents564
- AI483
- Developer Experience448
Weekly digest
The best engineering reads, once a week.