Nest handoff history by default #1996
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seratch
reviewed
Oct 29, 2025
rm-openai
previously requested changes
Oct 29, 2025
Collaborator
rm-openai
left a comment
There was a problem hiding this comment.
All of kaz's feedback seems right. In addition, I'd say two major things:
- This setting should be on the
Handoffobject - Since you're updating the default, this is a breaking change, so please update the changelog.
Merged
jhills20
commented
Nov 8, 2025
Contributor
Author
jhills20
left a comment
There was a problem hiding this comment.
moved to Handoff, added handoff history .py file for non extension parts of handoff filter, added changelog
rm-openai
reviewed
Nov 14, 2025
Comment on lines
+28
to
+29
| - By default handoff history is now packaged into a single assistant message instead of exposing the raw user/assistant turns, giving downstream agents a concise, predictable recap | ||
| - The existing single-message handoff transcript now by default starts with "For context, here is the conversation so far between the user and the previous agent:" before the `<CONVERSATION HISTORY>` block, so downstream agents get a clearly labeled recap |
Collaborator
There was a problem hiding this comment.
we;ve release 0.5.0 so you'll need to move this to a 0.6.0 section
Comment on lines
+1019
to
+1027
| filter_name = getattr(input_filter, "__qualname__", repr(input_filter)) | ||
| from_agent = getattr(agent, "name", agent.__class__.__name__) | ||
| to_agent = getattr(new_agent, "name", new_agent.__class__.__name__) | ||
| logger.debug( | ||
| "Filtering handoff inputs with %s for %s -> %s", | ||
| filter_name, | ||
| from_agent, | ||
| to_agent, | ||
| ) |
Collaborator
There was a problem hiding this comment.
weird syntax - also can you use f-strings and get rid of getattr?
Comment on lines
+20
to
+24
| __all__ = [ | ||
| "remove_all_tools", | ||
| "nest_handoff_history", | ||
| "default_handoff_history_mapper", | ||
| ] |
Collaborator
There was a problem hiding this comment.
can remove this, not super useful
seratch
requested changes
Nov 14, 2025
|
|
||
| When a handoff occurs, it's as though the new agent takes over the conversation, and gets to see the entire previous conversation history. If you want to change this, you can set an [`input_filter`][agents.handoffs.Handoff.input_filter]. An input filter is a function that receives the existing input via a [`HandoffInputData`][agents.handoffs.HandoffInputData], and must return a new `HandoffInputData`. | ||
|
|
||
| By default the runner now collapses the prior transcript into a single assistant summary message (see [`RunConfig.nest_handoff_history`][agents.run.RunConfig.nest_handoff_history]). The summary appears inside a `<CONVERSATION HISTORY>` block that keeps appending new turns when multiple handoffs happen during the same run. You can provide your own mapping function via [`RunConfig.handoff_history_mapper`][agents.run.RunConfig.handoff_history_mapper] to replace the generated message without writing a full `input_filter`. That default only applies when neither the handoff nor the run supplies an explicit `input_filter`, so existing code that already customizes the payload (including the examples in this repository) keeps its current behavior without changes. You can override the nesting behaviour for a single handoff by passing `nest_handoff_history=True` or `False` to [`handoff(...)`][agents.handoffs.handoff], which sets [`Handoff.nest_handoff_history`][agents.handoffs.Handoff.nest_handoff_history]. If you just need to change the wrapper text for the generated summary, call [`set_conversation_history_wrappers`][agents.handoffs.set_conversation_history_wrappers] (and optionally [`reset_conversation_history_wrappers`][agents.handoffs.reset_conversation_history_wrappers]) before running your agents. |
Member
There was a problem hiding this comment.
to make merging the code changes easier, can you make a separate pull request for document changes? with this, we can merge code first, and then merge document changes after thre release including the changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
nest_handoff_historyflag toRunConfigand call a new helper that condenses the prior transcript into a developer-role summary when handing offTesting
uv run pytest tests/test_extension_filters.pyuv run pytest tests/test_agent_runner.py -k handoffuv run pytest tests/test_agent_runner_streamed.py -k handoffhttps://chatgpt.com/codex/tasks/task_i_68ff73bda0f4832496f3d1fa9103905f