Find published dossiers by topic, company, product or technology.

Showing 1–20 of 107 dossiers

Amazon Aurora Serverless gets faster burst scaling

Aurora Serverless can now add roughly 12 ACUs in the first second of a scale-up event on platform versions 3 and 4. The change is automatic and is most useful for bursty SaaS, API, batch and agent workloads, but it does not remove the separate resume delay when a database has scaled all the way to zero.

Supabase fixes broken client trace propagation and now preserves trace IDs even for unsampled requests

supabase-js 2.112.3 materially improves the tracing rollout BTN covered earlier: unsampled requests now still carry traceparent for backend log correlation, tracing misconfiguration produces warnings, and browser Edge Function calls need current CORS headers to admit W3C trace context.

Safari 27 gives coding agents a local MCP path into live browser debugging

WebKit’s Safari MCP server turns browser debugging into an agent-callable interface. It runs locally and makes no network calls itself, but captured page data is sent directly to the connected agent, so browser-session trust and model data handling become part of the development security model.

OpenAI’s Codex client exposes a GenUI layer for refreshable interfaces inside conversations

RuntimeWire found a generic `genui` message path, a server-directed widget refresh endpoint and 467 versioned Learning Block manifests inside OpenAI’s Codex desktop client. The material development is not another visualization feature: it is evidence of a reusable interface layer beneath conversational answers, with important limits around what is actually public or enabled.

Agent Plugins 1.0 now has a concrete cross-client compatibility layer for Skills and MCP

Agent Plugins 1.0 now has documented support across VS Code, Cursor, GitHub Copilot, ChatGPT/Codex, Kiro and several open-source agents. That makes the format materially more useful for cross-client distribution, but portable components remain limited to Agent Skills and MCP servers while permissions, hooks, commands and host UX stay client-specific.

Railway makes MySQL automatic failover generally available with Group Replication and HAProxy

Railway’s managed MySQL path can now gain automatic failover without rebuilding the database elsewhere. The trade-off is real operational complexity: conversion briefly drops connections, hard-coded URLs need manual repair, replicas are for failover rather than read scaling, and each extra database/proxy node consumes billable resources.

Codex 0.149.0 ships asynchronous user messaging so agents can keep working after questions

Codex 0.149.0 includes the async-message tool, delivery metadata and removal of the client-side feature gate that BTN previously tracked only on main. Parallel human-agent work is now in a stable client, but late replies can still race with decisions and model capability metadata remains the final exposure gate.

Supabase makes MCP access centrally governed through enterprise SSO

Supabase has implemented MCP Enterprise-Managed Authorization using identity-provider assertions, short-lived tokens and existing Supabase role boundaries. It gives organizations a central on/off switch for approved AI clients while keeping access scoped to the individual employee rather than sharing a powerful organization token.

Cloud Run adds singleton instances for long-lived, individually addressable workloads

Cloud Run instances sit between autoscaling serverless services and a small VM. They run one individually addressable container continuously, can be stopped and restarted, and use shared CPU economics; Google’s launch example prices 1 vCPU plus 1 GiB running for 30 days at $5.70.

Google is temporarily restricting new Gemini API access from service accounts

The change creates an authentication compatibility boundary for server-to-server Gemini integrations: an architecture that works in an existing project may not be reproducible with a newly introduced service account, and Google has not published an end date for the restriction.

VS Code is moving coding agents into a standalone host with shared AHP sessions

Microsoft is rearchitecting VS Code around a dedicated Agent Host rather than treating each coding agent as an editor-bound extension. AHP gives different harnesses one shared session model, but the rollout is still active and VS Code 1.132 removed the administrator policy that had centrally disabled the Agent Host.