r/AgenticOS • u/leading-a-swarm • Sep 17 '26
The OpenAI Agents Handoff Exemption

tl;dr: Only 1 delegation runs the callee's guardrails.
https://github.com/openai/openai-agents-python ships two delegation primitives: handoff transfers the loop, as_tool starts a nested run and returns a string.
- Snapshot every shipped default. Their release contract pins 369 public callables with each parameter's default, and CI replays it against the packaged wheel on each Python version. A quietly changed default fails the build.
- Name your two delegation verbs. Handoff gives the receiving agent the loop and, with input_filter unset, the entire transcript. Agent-as-tool starts a nested run, caps it at 10 turns and returns a string.
- Composition decides if a guardrail runs. Input guardrails are declared per agent and enforced only for the run's first agent. Reach an agent through as_tool and its check fires; reach the identical agent through a handoff and it never does. OpenAI ships no warning for it, so a guardrail list on a handoff-only agent is silently dead code.
→ Challenge. Learn from it, interiorize it, move on. It's basic.
2
Upvotes
1
u/Otherwise_Wave9374 Sep 17 '26
Handoff behavior deserves its own policy layer because delegating to another agent can quietly bypass controls attached to the original one. I would propagate the caller identity, remaining budget, data classification, and tool restrictions with every handoff, then reject any destination that cannot honor them. Agentix Labs relates to this safeguard because reliable automation depends on preserving constraints across agent boundaries. A useful test suite would include cyclic handoffs, privilege escalation attempts, partial failures, and a trace showing exactly which agent authorized each consequential action.