Integrations
Your framework, checked step by step.
A decorator, a callback handler or a hook, depending on what your agents run on. The engine runs in your process either way.
SDK · Available
Kyvvu for Python
Put @kv.step on the functions your agent calls. Each call is checked against the task's path before it runs, and recorded after.
Framework · Available
Kyvvu for LangChain
One callback handler. Model calls, retrievers and tool calls are checked before they run, and every chain run becomes a task.
Framework · Available
Kyvvu for LangGraph
The LangChain handler works on graphs as they are. The LangGraph handler adds each step's node name and records interrupt() as an approval gate.
Framework · Available
Kyvvu for CrewAI
A listener on your crew. Tool and model calls are checked before they run, and the crew's final answer is checked before it's returned.
Coding agent · Available
Kyvvu for Claude Code
Claude Code's own hooks send every tool call to the engine first: Bash, Read, Write, Edit and the rest. No code changes.
Local engine · Available
Kyvvu for any language
For agents in JavaScript, Go, Rust or anything else: run the engine as a local HTTP sidecar and ask it before every step.
Logging · Available
Kyvvu for REST API
Register agents and send their traces to the platform over HTTP, from anything that can make a request.
Adapter · Available
Kyvvu for your own framework
Map your framework's events to Kyvvu steps in a YAML template, and capture them with a small adapter class.
Microsoft AutoGen and Semantic Kernel are planned: native adapters are in development. For agents in any language, see the local engine; for other frameworks, your own adapter.
Something else?