Support standalone named function call outputs (#39782)

## Why

External tool events may need to enter thread history without a preceding function call and therefore do not have a `call_id`.

## What changed

- Allow `function_call_output` items to omit `call_id` and carry optional `name` and `namespace` fields.
- Preserve named standalone outputs during history normalization and agent forks while retaining existing pairing behavior for outputs with a `call_id`.
- Accept, persist, and forward these outputs through `thread/inject_items`, and update the app-server schemas and documentation.

## Testing

- Cover paired and standalone JSON round trips, history normalization, agent forks, and injected thread history.

GitOrigin-RevId: a3258163a7dc93777c7c3023116fe204819bdbb0
This commit is contained in:
rka-oai authored and copyberry committed 2026-08-20 19:19:41 +00:00
1 parent 854cbb2fd4
commit 763787d061
42 files changed
+473 -114

No files matched your search

+6 -2
View File
@@ -107,7 +107,9 @@ async fn recent_image_fallback_selects_newest_images_in_chronological_order() {
},
ResponseItem::FunctionCallOutput {
id: None,
call_id: "mcp-call".to_string(),
call_id: Some("mcp-call".to_string()),
name: None,
namespace: None,
output: image_output("mcp"),
internal_chat_message_metadata_passthrough: None,
},
@@ -136,7 +138,9 @@ async fn recent_image_fallback_selects_newest_images_in_chronological_order() {
},
ResponseItem::FunctionCallOutput {
id: None,
call_id: "orphan-call".to_string(),
call_id: Some("orphan-call".to_string()),
name: None,
namespace: None,
output: image_output("orphan"),
internal_chat_message_metadata_passthrough: None,
},