What usually goes wrong
Crew-based systems can hide cost growth because work moves across multiple agents and tasks. A workflow can feel healthy while still spending too much or getting stuck in a handoff loop.
- One agent keeps asking another for more context
- Research tasks fan out longer than expected
- The team cannot see which run caused the spike until later
Start with a small integration
The right first step is still the SDK. Keep it local, wrap the run, and give yourself one visible cost boundary before you add more infrastructure.
from crewai import Agent, Crew, Task
from agentguard import BudgetGuard, JsonlFileSink, LoopGuard, Tracer
from agentguard.integrations.crewai import AgentGuardCrewHandler
tracer = Tracer(
sink=JsonlFileSink("traces.jsonl"),
service="crewai-crew",
)
loop_guard = LoopGuard(max_repeats=3, window=6)
budget_guard = BudgetGuard(max_cost_usd=5.00, max_calls=20)
handler = AgentGuardCrewHandler(
tracer=tracer,
loop_guard=loop_guard,
budget_guard=budget_guard,
)
agent = Agent(
role="researcher",
goal="Answer one short question clearly.",
backstory="You are concise and careful.",
llm="gpt-4o-mini",
step_callback=handler.step_callback,
verbose=True,
)
task = Task(
description="Explain what AgentGuard does in one short paragraph.",
agent=agent,
callback=handler.task_callback,
)
crew = Crew(agents=[agent], tasks=[task], verbose=True)
result = crew.kickoff()
print(result)
print("Traces saved to traces.jsonl")
Add the dashboard when operations stop being solo
A solo developer can tolerate more local workflow. A team cannot. That is when the hosted dashboard starts pulling its weight.
- Retained history across runs and services
- Alerts and remote kill for active incidents
- Team workflows and governance around guardrail actions
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 need alerts across multiple agents and runs.
- You need retained history for team debugging and reviews.
- You need remote kill and governance for shared production workflows.
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.