A live agent can now talk while it works, which makes cancellation and state reconciliation the new control

Automate

Foreground conversation, background execution, shared cancellation

Keep the user-facing conversation responsive while tools execute asynchronously, but bind both planes to one task identifier, one current-intent record, one permission snapshot, and one cancellation path.

Parallel conversation reduces perceived latency and makes long-running work usable, but it also allows the user's intent and the executing task to diverge. A shared cancellation and reconciliation protocol prevents the agent from completing an obsolete or no-longer-authorized action simply because the tool call was already in flight.

Trigger

Create a durable task identifier when the user authorizes background work. Record the exact requested outcome, the tools permitted, and the approval level before acknowledging that execution has started.

Foreground loop

Let the conversational model acknowledge, clarify, and narrate without pretending the background result exists. Every progress statement must be derived from task state rather than generated from the original plan.

Background executor

Run tools against a versioned intent and permission snapshot. Require idempotency keys for external writes so retries or resumed sessions cannot duplicate actions.

Reconciliation verifier

Before presenting or committing a result, compare it with the latest user instruction, current permissions, and task version. A technically successful tool call fails verification if the user changed or cancelled the goal.

Cancellation and escalation

Propagate user interruption to queued and running work, stop safely where possible, and surface any irreversible side effect that completed before cancellation. Route ambiguous or high-impact divergence to a human.

• Gemini 3.8 Live maintaining dialogue while tools and APIs execute in the background
• Gemini 3.8 Live Extended Thinking narrating multistep progress while deeper reasoning continues
• A support agent that keeps speaking while a refund check runs, but revalidates the requested amount before submission

Sources Google

2026-09-15 · Google · Cowork

Gemini 3.8 Live

Native speech-to-speech interaction with near-real-time visual grounding, automatic movement across 97 languages, and background tool or API execution while dialogue continues.

Operators should separate conversational responsiveness from task completion in telemetry and user experience. A smooth foreground must never be accepted as evidence that the background action succeeded, remained authorized, or still matches current intent.

Sources Google

2026-09-14 · GitHub · Build

Copilot automatic model selection tiers

Three routing policies let a user optimize automatic model selection for efficiency, balance, or intelligence while the service chooses a model per prompt from the same available set.

Engineering leaders should log the selected model, latency, cost, and outcome for every routed task. The policy name expresses intent, but only the route-level record can explain why spend or quality changed between otherwise similar sessions.

Sources GitHub Changelog

2026-09-18 · GitHub · Build

Agent Host local Dev Containers and pull-request creation

Agents can run with project tools and dependencies inside supported local Dev Containers, create pull requests directly from sessions, and optionally clean up inactive sessions after their pull requests merge.

A reproducible container narrows environment drift, but local execution inherits the developer machine's credentials and network reach. Pair the container definition with managed permissions, an explicit outbound-domain policy, and retained session evidence before enabling direct pull-request creation.

Sources GitHub Changelog

2026-09-15 · Salesforce · Cowork

AIforce Headless Toolkit

CRM data, workflows, business logic, semantics, permissions, security, and governance are exposed to Claude, Slack, Lightning, and partner-built agent interfaces.

The agent interface can change without moving the system of record, but permission enforcement and action logging must remain consistent across surfaces. Test the same restricted action through each interface and reconcile the resulting audit trail.

Sources Salesforce

2026-09-15 · Salesforce · Connector

AIforce Headless Toolkit and AgentExchange

A headless layer exposes MCPs, APIs, plugins, skills, workflows, and actions so third-party AI interfaces can use Salesforce context and Agentforce agents.

This makes the connector boundary more durable than the interface. Platform teams should inventory which permissions, semantic definitions, and audit records survive across Claude, Slack, Lightning, and partner surfaces before approving broad activation.

Sources Salesforce

2026-09-15 · Gemini Live API · Connector

Real-time media integration partners

Google lists Agora, Fishjam, LiveKit, LangChain, Pipecat, Vercel, and Vision Agents as integration partners handling media-streaming infrastructure for Gemini Live applications.

Media transport becomes a separate operational dependency from the model and tools. Buyers should record which partner terminates audio, where media is retained, how interruptions propagate, and whether end-to-end latency remains observable.

Sources Google

2026-09-18 · GitHub · Connector

Sentry integration in Copilot

The weekly Copilot release adds Sentry integration alongside code-review and agent-session updates, bringing production error context closer to the build agent.

Production telemetry can improve diagnosis, but it also expands the sensitive context available to an agent. Scope projects and fields explicitly, redact secrets, and verify that write authority does not arrive with read access.

Sources GitHub Changelog

Evidence · Vendor Claim

Microsoft · Cloud supply-chain monthly planning and demand-plan investigations

Across five monthly planning cycles from April through August 2026, average cycle time declined from about ten business days to less than 2.5 after more than 111 agents were deployed.

This is stronger than a generic productivity percentage because Microsoft names the workflow, period, team size, cycle count, baseline, and resulting duration, and states that explanations remained human-validated. It remains internal analysis without a control group, so use the shape of the measurement rather than importing the magnitude into a business case.

Sources Microsoft

Evidence · Vendor Claim

Salesforce · CRM actions such as updating opportunities, routing cases, and scheduling follow-ups

Salesforce reports that Koa matches or exceeds leading models on its CRM benchmark with three times fewer errors.

The named tasks make the claim testable, but the benchmark, absolute error rates, comparison roster, and evaluation method are not published. Reproduce the task set in the pilot and require absolute failure counts before using the multiple.

Sources Salesforce

Permissioning

Snapshot permission at task start and revalidate it before any external write. A live conversation can outlast the authorization that launched its background tool, especially when users switch accounts, roles, or intent mid-turn.

Verification

Verify against the latest task version, not the original prompt. A successful tool result is invalid if the user cancelled, changed the requested outcome, or supplied newer evidence while the background work was running.

Auditability

Use one task identifier across foreground dialogue, model routing, tool calls, approvals, retries, and final disposition. Concurrent execution is not auditable when each plane emits an unrelated session log.

Cost

Meter the entire workflow: audio input, audio output, reasoning, tools, retries, media transport, and idle open-session time. A low voice rate can coexist with an expensive background execution path.

Reliability

Require idempotency keys and explicit cancellation semantics for every side-effecting tool. Retrying or resuming a background task must not duplicate a payment, ticket, message, or production change.

Interrupt a background task and prove nothing stale can commit

Expected outcome: You will have evidence that conversational continuity cannot cause an obsolete task to commit, plus a concrete gap list for cancellation propagation, permission revalidation, idempotency, and cross-plane audit correlation.

• Choose a harmless workflow with a delayed tool call, such as drafting but not sending a status message, and assign one durable task identifier to the conversation and tool execution.
• Start the task, then interrupt with a materially changed instruction before the tool returns. Record the new task version and issue cancellation to the old version.
• Let the original tool call return and confirm the verifier rejects its result because it no longer matches current intent, even though the tool itself succeeded.
• Repeat with a permission revocation and with a network retry. Confirm the idempotency key prevents duplicate side effects and the audit record links both attempts.

Sep 21-30

Gemini Live cancellation and session semantics

Developer documentation needs to state how background tool calls behave when the user interrupts, disconnects, or changes intent.

Oct 2026

Koa pilot error evidence

Absolute task-level failure counts would turn a vendor multiple into an actionable verification target.

Next GitHub release

Route-level cost and selected-model telemetry

Policy tiers become governable only when organizations can export which model ran, what it cost, and whether the task succeeded.

Q4 2026

Microsoft supply-chain measurement update

Additional planning cycles would show whether the reported duration reduction persists beyond five observations.

• Lead technique changed from independent verification in W37 to shared cancellation and reconciliation for concurrent conversational execution.
• Proof quality remains explicit: Microsoft's bounded internal analysis and Salesforce's proprietary benchmark are both labeled vendor claims.
• All product and pricing claims are sourced to public material dated September 14-19, 2026.