Skip to main content
Both AutoGen and CrewAI can target OpenAI-compatible endpoints, which makes Xenovia a good fit. The main job is to point the framework at your Xenovia proxy URL and keep a stable session header for the whole run.
AutoGen has multiple major-package eras in the wild. The example below uses the current autogen-agentchat and autogen-ext[openai] packages rather than the older pyautogen setup.

AutoGen

If your AutoGen client version exposes default request headers, add a stable X-Xenovia-Session-Id there so every turn lands in the same Xenovia session.

CrewAI

How multi-agent traces work

In multi-agent setups, each agent turn is a separate call through the proxy. Each call:
  • Gets its own X-Xenovia-Trace-Id
  • Is evaluated independently by the request-stage Rego policy
  • Is grouped under the shared X-Xenovia-Session-Id
Filter by session_id in the Traces view to reconstruct the full agent conversation in order, with per-turn policy decisions and intent scores.

Handling policy blocks

When a request is blocked by policy, AutoGen and CrewAI surface the upstream 403. Add framework-level error handling around the top-level run call so you can log the failure and trace ID cleanly.