Start one from first-run setup with Protect your agent, or in Settings › Integrations under AI apps and platforms. You need to be an admin of your Xenovia organization. Each integration keeps its keys and signing secrets encrypted and never shows them again. Choose Sync now on the integration page to sync right away.
Claude Platform
- Discovery. Xenovia lists every Managed Agent in the workspace, with its model, MCP servers and each risky tool’s permission policy. Each one shows up in Discovery.
- Checks. A Managed Agent tool set to
always_askpauses the session before it runs. Claude Console’s webhook tells Xenovia, and Xenovia answers each paused tool call with allow, or deny with the reason.
Before you start
- In Claude Console, create an API key in the workspace your Managed Agents run in.
Connect Claude Platform
1
Open the integration
In Settings › Integrations, find Claude Platform under AI apps and platforms and choose Connect.
2
Paste the key
Paste the key into Claude API key and choose Connect. Xenovia checks that the key can list the workspace’s Managed Agents. If the check fails, Xenovia shows why and saves nothing.
3
Add Xenovia's webhook
The Send prompts to Xenovia step shows the webhook address for this connection. In Claude Console, open the workspace’s webhooks and add an endpoint with that address for the
session.status_idled event. Claude Console shows a signing secret that starts with whsec_. Paste it into Webhook signing secret: in the dialog, or later with Settings on the integration page.4
Ask before risky tools run
In each Managed Agent, set the tools Xenovia should check to
always_ask.The agents Xenovia creates
Connecting creates a Xenovia agent called Claude Managed Agents. After each listing, every Managed Agent also gets a Xenovia agent of its own, named after it, which its paused tool calls are checked as. An entry you linked to another agent keeps that agent. The agents stay drafts until the signing secret is set, and go live once it is. Set each agent’s Neon protections and policies on its page, as for any agent. Each checked tool call is recorded in Sessions.What Xenovia reads
Xenovia only reads listings. It never changes an agent or a session; it only answers the paused tool calls.
A Managed Agent’s page in Discovery shows how many of its tools Xenovia checks, its MCP servers, and each tool’s policy: asks first, runs without asking, or Anthropic decides. Discovery reports a finding when:
- risky tools run without asking, so Xenovia never checks them,
- MCP tools of a server run without asking,
- the agent can run in an environment that can reach any website.
always_ask in Claude Console.
Choose Sync now on the integration page to sync right away. Recent syncs shows how the last ones went.
How a paused call is answered
When a session pauses, Xenovia reads its paused tool calls with the workspace key, checks each as the Managed Agent’s Xenovia agent, and answers each one. The webhook delivery is acknowledged at once; the checks run after. A call is denied when a check finds a problem and the agent enforces. If Xenovia can’t check a call, it denies it when the agent enforces, because the session would otherwise wait for ever, and allows it when the agent only monitors.Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing, deletes the stored key and signing secret, and turns the connection’s agents off. Open findings from Claude Platform are resolved, and Managed Agents only it reported leave Discovery. Your reviews are kept. Remove Xenovia’s webhook from Claude Console too, and revoke the API key. Paused sessions are no longer answered by Xenovia.Troubleshooting
Troubleshooting
Claude Enterprise
- Discovery. Through Claude’s Compliance API, Xenovia lists the people in your Claude organization and which Claude products each uses: Claude chat, Claude Code and Cowork. Each product shows up in Discovery with the people who use it.
- Checks. Through Claude’s inference hook, Claude asks Xenovia about each prompt and each tool call before it acts. Xenovia allows it, or denies it with a reason.
Before you start
- In Claude Enterprise settings, create a Compliance access key with read access to the Compliance API. Xenovia never asks for delete access.
Connect Claude Enterprise
1
Open the integration
In Settings › Integrations, find Claude Enterprise under AI apps and platforms and choose Connect.
2
Paste the key
Paste the key into Compliance access key and choose Connect. Xenovia checks the key against the Compliance API. If the check fails, Xenovia shows why and saves nothing.
3
Add the inference hook
The Send prompts to Xenovia step shows the hook address for this connection. In Claude’s admin settings, add an inference hook with that address. Claude shows a signing secret that starts with
whsec_. Paste it into Inference hook signing secret: in the dialog, or later with Settings on the integration page.The agents Xenovia creates
Connecting creates Xenovia agents that the hook’s prompts and tool calls are checked as:
Each product’s Discovery entry is governed by its own agent. The agents stay drafts until the signing secret is set, and go live once it is. Set each agent’s Neon protections and policies on its page, as for any agent. Each checked prompt and tool call is recorded in Sessions under its agent.
If you disconnect and connect again, the Claude Enterprise agent comes back with its history.
What Xenovia reads
The first sync reads the last 30 days. Later syncs continue from where the last one stopped. Xenovia only calls listing endpoints. It never reads the contents of messages or transcripts, and never deletes anything.
Choose Sync now on the integration page to sync right away.
How the hook answers
- For a prompt, Xenovia checks the latest user message, with its attachments’ text.
- For a tool call, Xenovia checks each tool call the model wants to make.
Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing, deletes the stored key and signing secret, and turns the connection’s agents off. Open findings from Claude Enterprise are resolved, and entries only it reported leave Discovery. Your reviews are kept. Remove the inference hook from Claude’s admin settings too, and revoke the Compliance access key in Claude Enterprise.Troubleshooting
Troubleshooting
OpenAI Platform
Before you start
- In OpenAI’s organization settings, open Admin keys and create one. Only organization owners can.
Connect OpenAI Platform
1
Open the integration
In Settings › Integrations, find OpenAI Platform under AI apps and platforms and choose Connect.
2
Paste the key
Paste the admin key into OpenAI admin key and choose Connect. Xenovia checks that the key can list your projects. If the check fails, Xenovia shows why and saves nothing.
What Xenovia reads
Every hour, Xenovia reads each active project’s API keys: the key’s name, its owner, when it was last used, and its requests, tokens and models over the past 7 days. It only calls listing endpoints. Choose Sync now on the integration page to sync right away. Recent syncs shows how the last ones went.Through Xenovia, or direct
After each sync, Xenovia compares each key with the OpenAI providers in your Xenovia organization:
To bring a direct key under Xenovia, add it as an OpenAI provider in Xenovia and point the app that uses it at a Xenovia agent. See Supported providers and Connect your app. After the next sync, the key shows Through Xenovia: Yes.
Each key’s page links to the project’s keys in OpenAI with Open the project’s keys.
Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing and deletes the stored admin key. Open findings from OpenAI Platform are resolved, and keys only it reported leave Discovery. Your reviews are kept. Delete the admin key in OpenAI’s organization settings too. To use a different admin key, choose Settings on the integration page. Xenovia checks the new key before saving it.Troubleshooting
Troubleshooting
What next?
Neon
Set what each platform agent enforces.
Coding agents
Govern Claude Code, Codex and Cursor through their hooks.
Discovery
Review what the platforms reported.