Systems | Development | Analytics | API | Testing

AI Transport v0.5.0 is now available. It adds first-class support for running an agent turn inside a durable execution framework, such as Temporal or Vercel's Workflow Development Kit (WDK), while every client watching the conversation still sees one clean, resumable stream. The last release, v0.4.0, let an agent hydrate its history from your own database. This one is about what happens when the process running the agent isn't around for the whole turn.

What an incredible day at the Agentic Analytics Playbook EMEA event! It might have been baking hot outside, but inside the Nobu Hotel, the energy was absolutely electric.

Test execution is one of the most time-sensitive stages of software delivery. Teams are expected to validate functionality, ensure stability, and support release decisions within increasingly shorter development cycles. Even with strong automation in place, there is rarely enough time to execute every Test before a release. This makes prioritization a critical part of the QA process.

TL;DR: Tableflow is a Confluent Cloud feature that materializes Apache Kafka topics as Apache Iceberg or Delta Lake tables, eliminating custom data pipelines by automatically handling schematization, type conversions, schema evolution, CDC stream materialization, catalog publishing, and table maintenance.

Connecting Salesforce to Claude via MCP is the advancement the SERP says it is. You authenticate once, your AI agent queries live CRM data, and you stop copying deal records into chat windows. For a Revenue Operations Manager who spent Q1 begging an admin to export pipeline snapshots, that matters.

86% pick generative AI before any BI tool for analytical work. Trust ranks fourth in their reasons. Speed and convenience rank first.

HTTP works fine for a chatbot that responds in seconds. Add token streaming, and it mostly still works. But once an agent starts doing things that take real time, reasoning across multiple tool calls, spawning sub-agents, running for minutes instead of milliseconds, the UX starts to falter. The connection drops while the agent is mid-thought. The user switches tabs, comes back five minutes later, and the session is gone. The agent finishes its work, but the client has already moved on.