What happens when an OpenAI Agents SDK guardrail trips?

An agent-level tripwire stops the run and raises InputGuardrailTripwireTriggered or OutputGuardrailTripwireTriggered. A blocking input guardrail catches the request before the agent starts; the default parallel mode can spend tokens or call a tool before the tripwire lands. A function-tool guardrail has another choice: reject the call or result and let the agent continue, or raise a tool-scoped tripwire exception and stop it. The SDK documents both paths.

The decision survives the exception. An agent tripwire carries guardrail_result, and its input or output results include the check that fired. A tool tripwire carries guardrail and output directly; its run_data lists hold earlier completed tool checks, not the triggering result. The SDK documents the exception fields. Counting trips from the agent-level result list alone will miss tool trips.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y