TanStack AI reaches 1.0 with stable agent toolkit

What changed: TanStack published a 1.0 release of its TanStack AI stack, stabilizing 76 packages and formally supporting agents, subagents, coding-agent workflows, sandboxes, provider adapters, and an experimental harness for running agents in multiple environments. The post lists concrete additions (portable agent skills, subagents, computer-use tooling, MCP server support, and 23 provider adapters) and upgrade steps for existing 0.x users.

Why it matters: Builders who need a portable, framework-agnostic agent runtime can now rely on a stable open-source API to run chat UIs, tool-calling agents, and coding agents across providers and sandboxes — reducing lock-in and integration work when swapping model providers or embedding agents in web apps and editors.

Try/watch: If you ship agent features, run the TanStack 1.0 quickstart in a staging environment and validate your provider adapter (OpenAI, Anthropic, or local) and sandbox paths; watch the harness APIs closely — they’re marked experimental and could change in minor releases.

F5 and Google Cloud describe integration patterns to secure agent fleets

What changed: F5 published a technical blog describing how Google Cloud’s Agent Gateway can pair with F5 AI Guardrails to centralize routing, policy enforcement, and prompt/API inspection for fleets of agents at enterprise scale. The post explains an architecture where Agent Gateway handles traffic control while F5 inspects prompts and agent tool calls to block sensitive data and malicious intent in real time.

Why it matters: Enterprises moving from single agents to hundreds or thousands of agent deployments need centralized controls to avoid policy drift, accidental data leaks, and inconsistent access rules; this integration shows a practical path to inherit security and auditability without rewriting each agent.

Try/watch: Pilot Agent Gateway + F5 Guardrails on a non-production fleet, instrument event-level logging for agent-to-tool calls, and measure how many agent behaviors require human review versus automated enforcement; monitor for false positives on prompt inspection that could break legitimate workflows.

Material Security launches a Google Drive Security “agent” for workspace risk remediation

What changed: Material Security announced a Google Drive Security Agent that inspects Drive content and sharing patterns, synthesizes findings, and can remediate over-permissioned files automatically — aimed at risks introduced when third‑party AI tools get OAuth access to workspaces. The release cites an internal study about widespread exposure when agents or tools are granted access and positions the product as an automated remediation layer for that risk surface.

Why it matters: For buyers and security teams, this is a concrete example of agent-aware tooling: instead of treating agents as invisible users, security tooling now treats agent access and behavior as first-class telemetry and can automate remediation where manual triage doesn’t scale.

Try/watch: If your org allows third‑party AI integrations, inventory OAuth grants and run a scoped pilot of Material Security’s Drive agent (or equivalent) to see whether automated remediation reduces your exposure; track how often the agent’s decisions need human override to tune policies.