What it does
You ask a Kubernetes question or describe an incident. The agent puts it to Klaudia, who investigates across the clusters your Komodor account already covers, and relays the answer back — as prose for a question, or as a structured root-cause analysis when that is what she produces. Unlike the in-cluster investigators, it is not bound to one cluster. Its reach is whatever your Komodor account’s agent already sees.What it reads
It reads nothing directly. Its entire surface is a small, fixed set of tools for holding a conversation with Klaudia — asking a question, collecting the result, and nothing else. The investigation happens on Komodor’s side. Because that surface is fixed by the agent itself, the wizard’s tool checklist has no effect on it: what it can do is decided by the implementation, not by what you tick.Before you deploy
There is no Komodor connection to create. The Komodor MCP server authenticates itself on the gateway
server object, configured once in gateway administration, so the Integrations step has nothing to
collect for this agent — only the MCP group needs binding.
Ask it for
In chat, or as a run’s prompt:How a pause reaches you
Klaudia can stop mid-investigation to ask for an approval or a choice. When she does, the agent does not answer on your behalf — the pause is surfaced back as a decision waiting for a person, and the investigation resumes once someone answers it. See Approvals for where those decisions land and who may make them.Defaults and limits
In a workflow
It is the multi-cluster counterpart to the in-cluster investigators: where a step needs a Kubernetes answer but the cluster is not known in advance, this is the specialist to route to. An orchestrator can also use it as a first pass, then delegate to a cluster-bound investigator once the affected cluster is identified. See Orchestration for how a step delivers work to it.What it will not do
It cannot answer an approval or a choice on your behalf. That is enforced in the agent rather than by configuration, so a gate Klaudia raises always comes back to a human. It also performs no investigation of its own. Everything it reports comes from Klaudia, so what it can see is exactly what your Komodor account covers — no more, and no less.Next steps
Approvals
Where a paused decision lands, and who may answer it.
Remediation Executor
Hand a finished investigation to Klaudia to act on.
Kubernetes RCA
In-cluster investigation with no Komodor backend.
Agent catalog
Every catalog agent, side by side.