BuildSubscribers only Jul 14, 2026 at 15:446Add to bookmarks

Google releases a preview of the Genkit Agents API for TS and Go, with detached turns (the agent survives disconnection) and HITL with anti-forgery validation - two building blocks that post-mortem agents have been requesting for twelve months.
In plain terms. Google has released a preview of the Genkit Agents API for TypeScript and Go. It wraps message history, tool loop, streaming, and persistence behind a single chat(). Two standout features are detached turns (the agent continues even after the client disconnects) and a HITL with anti-forgery validation on resume.
InfoQ (July 14, 2026) reports the preview release. Genkit already aimed at orchestrating prompts and flows; adding a stateful agent layer changes the game for teams that don't want to recode a custom harness. The interesting primitive is the detached turn: the API knows that an inference turn can last several minutes, that the client (browser, worker) will lose connection, and that a server-side job store must keep control. It's the missing piece between "instant chat" and "long-running agent that reminds the user in twenty minutes."
The HITL is not a marketing checkbox: interruptible tools require anti-forgery proof on resume, human validation, and the call resumes with a signed token. This is exactly what agent post-mortems in production have been asking for—a year to properly stop a tool call and resume without re-emitting the entire state.
Under the hood - The preview API exposes, according to the documentation quoted by InfoQ: unified TS/Go
chat(); pluggable message history and state persistence; streaming; interruptible tool loop; detached turns via server-side job identifier. For a custom harness already using LangGraph or a custom queue, the real question is: is Genkit'schat()surface extensible enough to connect your memory store (pgvector, DynamoDB) and your policy engine? In preview, the answer is probably "yes for standard cases, no for the edge."
So what. Google is fueling the market for pre-built harnesses (see also Adaptive Recall, the MCP memory wave, the arXiv "Better Harnesses, Smaller Models"). For a CTO shipping an agent in 2026, the question shifts from "which model?" to "which harness?" Genkit joins the shortlist alongside AI SDK, LangGraph, and Semantic Kernel. The risk: Google Cloud lock-in on persistence and authentication. To watch: the stable availability of the API, and whether detached turns hold up under load for 5-30 minute agents in production.
Create a free account to access all our content and the weekly review.
Article produced by artificial intelligence, reviewed under human editorial control.
Sign in to join the discussion.
Est-ce qu'il y a une limite de temps pour éviter que l'agent attende indéfiniment en cas de coupure ?
Exactement, et surtout : comment ça gère les coupures longues ?
Comment Google va gérer la validation humaine ? Ça sera automatique ou il faudra valider manuellement ?
Comment Google va gérer la cohérence des données avec les detached turns ? Y a-t-il des risques de conflits ?
Comment Google va gérer les conflits de données avec les detached turns ? Est-ce que ça va être fluide ?
Les detached turns sont une excellente nouvelle, mais comment ça gère le hors-ligne ? Y a-t-il un mécanisme de synchronisation à la reconnexion ?
Comment Google garantit-il la sécurité des données en mode déconnecté ?
Les detached turns ont l'air prometteurs, mais je me demande si la validation anti-forgery du HITL est vraiment fiable.
Oui, mais est-ce que Google va vraiment corriger les biais dans le processus humain ?
Harness Ops : post-mortems et bench des agents en prod