Back to Signal Feed
CodeTracked since May 22, 2026

Emit completed tool responses before confirmation requests

In google/adk-go, `runOneStep` now yields the merged tool function-response event before yielding `adk_request_confirmation`. This ensures a completed tool result is written to session history even when a consumer stops at the confirmation boundary.

runOneStepadk_request_confirmationfunction-response eventsession history

What Happened

  • In google/adk-go, `runOneStep` now yields the merged tool function-response event before yielding `adk_request_confirmation`. This ensures a completed tool result is written to session history even when a consumer stops at the confirmation boundary.
  • In google/adk-go, `runOneStep` now yields the merged tool function-response event before yielding `adk_request_confirmation`. This ensures a completed tool result is written to session history even when a consumer stops at the confirmation boundary.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Reordered the event stream so completed tool responses are emitted first, preserving session-history correctness for human-in-the-loop tool flows.

Why Track This

Why It Matters

Tool-call frameworks and operators using adk-go will no longer lose completed tool outputs when execution pauses for user approval, so downstream state, replay, and audit flows stay consistent instead of appearing to stop at a confirmation-only snapshot. Technically, the change emits the merged function-response event before the confirmation event; teams should watch custom consumers for implicit ordering assumptions and add/adjust tests around stop-at-confirmation behavior.

Impact

Tool-call frameworks and operators using adk-go will no longer lose completed tool outputs when execution pauses for user approval, so downstream state, replay, and audit flows stay consistent instead of appearing to stop at a confirmation-only snapshot. Technically, the change emits the merged function-response event before the confirmation event; teams should watch custom consumers for implicit ordering assumptions and add/adjust tests around stop-at-confirmation behavior.

What To Watch Next

  • Watch whether runOneStep becomes a repeated pattern.
  • Track follow-up changes around Tool Calling.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: consumer_order_assumptions, session_history_gap_regression.
Open Topic TimelineOpen Technical EventOpen Original Sourceconsumer_order_assumptions / session_history_gap_regression / stop_at_confirmation_behavior_changes

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

google/adk-go PR #765: fix: yield tool responses before confirmations

The PR fixes event ordering in tool execution streams so confirmation prompts no longer interrupt persistence of the already-computed function response.