You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Update docs with detailed guidelines on how to deploy guardrail models. #1097
so quick question — are you deploying guardrail models through the superagent docker setup or running locally? we hit this at scale when spinning up with Compose, turns out the docs gloss over the actual env config you need for guardrails. honestly, adding a sample guardrails_config.yaml and setting GUARDRAILS_MODEL_PATH in your env made it way less painful. here's the pattern we've been using:
# guardrails_config.yamlmodel_path: /models/guardrails-v1.binthreshold: 0.85log_level: info
then just pass that in with SUPERAGENT_CONFIG=/configs/guardrails_config.yaml in your docker env. not gonna lie, took us a few tries because the docs didn't mention the path casing and it threw silent errors.
Activity
rehan243 commentedon May 21, 2026
so quick question — are you deploying guardrail models through the superagent docker setup or running locally? we hit this at scale when spinning up with Compose, turns out the docs gloss over the actual env config you need for guardrails. honestly, adding a sample
guardrails_config.yamland settingGUARDRAILS_MODEL_PATHin your env made it way less painful. here's the pattern we've been using:then just pass that in with
SUPERAGENT_CONFIG=/configs/guardrails_config.yamlin your docker env. not gonna lie, took us a few tries because the docs didn't mention the path casing and it threw silent errors.