Once an agent is live, the questions change: why did it loop nine times, which step burned the tokens, what did it actually send. AgentOps records sessions so you can replay them instead of guessing from logs.
Reach for it when
- You have an agent in production and cannot see inside it
- Token spend is surprising you
- You need to replay a failed run exactly
Look elsewhere when
- You are still prototyping locally
- Your framework's built in tracing is enough
What the lessons will cover
- 01Install and setup
- 02Sessions and events
- 03Tracing an agent
- 04Cost tracking
- 05Replaying a run
- 06Alerts
- 07Framework integrations
- 08Reading a real trace
Others in infrastructure
LiteLLMOne interface in front of a hundred providers.
E2BSandboxes so agents can run the code they write.
MastraThe TypeScript agent framework, batteries included.Common questions
Is AgentOps free to use?
AgentOps is open source and free to run yourself. You still pay whichever model provider you point it at, and this tutorial is free with no signup.
Do I need to know Python to use AgentOps?
Basic Python is enough. Functions, dictionaries and imports cover most of what AgentOps asks of you.
When should I not use AgentOps?
You are still prototyping locally. Your framework's built in tracing is enough.
Lessons for AgentOps are being written. Meanwhile the LangGraph tutorial covers the same ground: state, tools, loops, memory and human approval. Most of it carries straight over.
Start the LangGraph tutorial →