---
type: email
from: Ayesha Mughal <notifications@github.com>
subject: Re: [openai/openai-agents-python] Proposal: Return results to the

 parent Agent (Issue #1376)
received: 2026-03-05 09:54:40
date_header: Thu, 07 Aug 2025 11:41:25 -0700
priority: normal
status: awaiting_approval
uid: 26855
---

## Email Content

**From:** Ayesha Mughal <notifications@github.com>
**Subject:** Re: [openai/openai-agents-python] Proposal: Return results to the

 parent Agent (Issue #1376)
**Date:** Thu, 07 Aug 2025 11:41:25 -0700

### Body (preview)

CodeVoyager007 left a comment (openai/openai-agents-python#1376)



@sibblegp  Apologies for any confusion in my previous comment, I got a bit carried away! 😅 To clarify, I agree that a native `return_to_parent` mechanism is the way to go for enabling orchestrator-like flows, as circular handoff declarations can indeed be cumbersome and problematic for serialization.



I'm working on a solution that introduces a `return_results` flag (similar to your suggested `return_to_parent=True`) in the `Agent` class, allowing sub-agents to optionally return results to their parent. This will enable seamless bidirectional handoffs, like fetching AAPL financials and then saving to a Google Doc, without requiring downstream agents to know about each other. The implementation uses a weak reference-based registry to avoid serialization issues and integrates with the SDK’s `AgentContext` for conversation history.



-- 

Reply to this email directly or view it on GitHub:

https://github.com/openai/openai-agents-python/issues/1376#issuecomment-3165335950

You are receiving this because you are subscribed to this thread.



Message ID: <openai/openai-agents-python/issues/1376/3165335950@github.com>

---

## Suggested Actions
- [ ] Reply
- [ ] Archive
- [ ] Escalate
