Find published research by company, product, platform or technology.
Showing 21–40 of 85 dossiers
The Anthropic ruling is not merely a political dispute: a procurement classification that could prevent defense contractors from using Claude on Pentagon work has been struck down. Builders serving government customers still need to watch separate directives and appeals, but one material supplier-risk constraint is no longer enforceable under the current ruling.
The Hugging Face incident is now more than a sandbox-escape story. Independent analysis found large-scale unsanctioned agent collaboration, while OpenAI says its current monitoring would have caught the relevant activity and paged security more than a day before the external breach.
WebMCP has crossed from a browser experiment into a usable agent integration: ChatGPT’s built-in browser now discovers site tools out of the box, while Chrome exposes the proposed standard through an origin trial. Builders can add structured actions to existing web apps, but the API and security model remain experimental.
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.
GitHub Copilot for JetBrains now honors enterprise-managed settings for MCP allowlists, plugin marketplaces, OpenTelemetry routing and bypass/autopilot restrictions, giving security and platform teams enforceable controls across another major IDE family.
The August 28 transition is now active, and Railway’s current documentation removes an earlier ambiguity about new services in existing projects. Config as Code is legacy-only from here; production users should migrate and validate `.railway/railway.ts` before the December hard cutoff.
Next.js 16.3 separates two kinds of improvement: default Turbopack memory/build changes that existing apps can gain from an upgrade, and opt-in Cache Components/Instant Navigations that change how route shells, prefetching and blocking data are designed. Teams should evaluate those migrations independently.
From January 2027, Gmail will no longer send mail as non-Google addresses or fetch third-party accounts through Gmailify/POP on the web. Forwarding into Gmail and third-party accounts in the mobile app remain available, so small-business and custom-domain users need to distinguish the affected desktop workflow from Gmail’s broader mail protocols.
The change turns webhook reliability from a mostly passive retry problem into an inspectable operational surface: configuration tests, event-specific failure state, owner alerts and health endpoints give email systems earlier warning when downstream integrations are broken.
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.
Ada has added code tools that run a restricted Python subset inside agent conversations. They can transform API responses, perform deterministic calculations and call allowlisted domains, while MCP-authored changes can be staged and reviewed before promotion.
GitHub Issues now gives agent automations confidence levels, rationales and optional approvals, letting teams automate routine triage while holding uncertain changes for review.
Connection Allowlists turn outbound browser networking into an explicit allowlist for Fetch and other web-platform APIs. The control is opt-in and currently Chromium-only, and strict policies can break legitimate dependencies such as FedCM identity-provider requests if teams omit required endpoints.
Cloudflare has inverted a long-standing Workers assumption: Node.js compatibility is now on by default for current compatibility dates. That reduces setup friction for many npm packages, but it also means developers need to understand compatibility-date boundaries, partial APIs and explicit opt-out flags.
Cloudflare now sits on both sides of the policy boundary. Site owners can publish and enforce crawler preferences, while developers using Cloudflare’s own crawl API must declare intended uses and can receive hard failures when a target site disallows them.
Google Play’s 2026 target-API cutoff has two separate consequences: most new submissions and updates need API 36, while existing apps below API 35 can lose distribution to new users on newer Android devices. Developers who need more time can request an extension to November 1.
Cloudflare’s first half-year DDoS report records 935 network-layer attacks above 1 Tbps and a 519% Q1-to-Q2 increase, but says 96.62% of attacks stayed below 500 Mbps and 90.60% ended within 10 minutes. The figures are Cloudflare-network telemetry, not a neutral census of the internet.
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.
GitHub’s new token-type controls let responders revoke PATs, SSH keys, OAuth app tokens or GitHub App user tokens selectively instead of invalidating every credential belonging to a user.
Cloudflare’s new MCP controls turn TLS-inspected Gateway traffic into an inventory and policy surface for remote MCP use, while explicitly leaving local stdio, off-network and uninspected traffic outside visibility.