What LangChain users actually need
Most teams do not need another generic observability layer on day one. They need confidence that a chain will stop before it gets expensive or weird.
That means budget awareness, loop detection, and a path into a hosted control plane only when the project becomes a team concern.
Use the SDK as the entry point
The fastest path is one install command and one callback handler. That keeps the first adoption step small enough that developers will actually try it.
from agentguard import BudgetGuard, JsonlFileSink, LoopGuard, Tracer
from agentguard.integrations.langchain import AgentGuardCallbackHandler
from langchain_openai import ChatOpenAI
tracer = Tracer(
sink=JsonlFileSink("traces.jsonl"),
service="langchain-agent",
)
loop_guard = LoopGuard(max_repeats=3, window=6)
budget_guard = BudgetGuard(max_cost_usd=5.00, max_calls=20)
handler = AgentGuardCallbackHandler(
tracer=tracer,
loop_guard=loop_guard,
budget_guard=budget_guard,
)
llm = ChatOpenAI(model="gpt-4o-mini", temperature=0)
response = llm.invoke(
"Give me a one-line summary of AgentGuard.",
config={"callbacks": [handler]},
)
print(response.content)
print("Traces saved to traces.jsonl")
What the dashboard adds later
Once a LangChain app is shared across a team, local success stops being enough. You need history, alerts, remote kill, and governance in one hosted place.
- Alerts for loops and cost spikes
- Retention for shared debugging and review
- Hosted control for remote kill and team workflows
When the paid dashboard is the right next step
The SDK should stay the first move. The dashboard becomes worth paying for when the same guardrails need to work as a hosted team system.
- You want alerts when a chain starts looping.
- You want retained trace history instead of one local test run.
- You want shared visibility and remote kill for production operations.
Try the small version first
Start with the free SDK, prove the guardrail locally, and only then move into the paid dashboard for alerts, retention, remote kill, team workflows, and governance.