Skip to content

Docs: Clarify that guardrails apply to both user input and agent output #1482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 14, 2025

Conversation

Abbas-Asad
Copy link
Contributor

Summary

Clarified the OpenAI Agents SDK documentation on guardrails to indicate that they apply to both user input and the agent's output, preventing misunderstandings about their scope.

Problem

The existing documentation stated:

"Guardrails allow you to run checks/validations on user input, in parallel to the agent running. For example, you could screen the user's input for relevance."

This wording implied that guardrails are only applicable to user input, omitting the fact that they can also run on agent output. This could mislead developers into underutilizing guardrails for output validation and filtering.

Changes Made

Updated the documentation sentence from:

Guardrails allow you to run checks/validations on user input, in parallel to the agent running. For example, you could screen the user's input for relevance.

To:

Guardrails allow you to run checks/validations on user input in parallel to the agent running, and on the agent's output once it is produced. For example, you could screen the user's input and agent's output for relevance.

## Summary

Clarified the OpenAI Agents SDK documentation on guardrails to indicate that they apply to both user input and the agent's output, preventing misunderstandings about their scope.

## Problem

The existing documentation stated:
> "Guardrails allow you to run checks/validations on user input, in parallel to the agent running. For example, you could screen the user's input for relevance."

This wording implied that guardrails are only applicable to **user input**, omitting the fact that they can also run on **agent output**. This could mislead developers into underutilizing guardrails for output validation and filtering.

## Changes Made

Updated the documentation sentence from:

> Guardrails allow you to run checks/validations on user input, in parallel to the agent running. For example, you could screen the user's input for relevance.

To:

> Guardrails allow you to run checks/validations on user input in parallel to the agent running, and on the agent's output once it is produced. For example, you could screen the user's input and agent's output for relevance.
@seratch seratch added the documentation Improvements or additions to documentation label Aug 14, 2025
@seratch seratch merged commit 7560cab into openai:main Aug 14, 2025
6 checks passed
vcshih pushed a commit to veris-ai/openai-agents-python that referenced this pull request Aug 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants