Skip to main content
Deploy this agent when a decision has been made and something has to actually change. It takes a completed investigation and delegates the fix, choosing between the live cluster and the source repository depending on how you configure it. This page covers both paths, the approval boundary it cannot cross, and where it stops.

What it does

It consumes the same input envelope as Remediation — a completed investigation’s findings — and hands the work to a system that can carry it out. It does not re-investigate; it instructs, and relays a typed outcome back. Which one it uses is a configured choice, not something it decides mid-run.

What it reads

Before you deploy

GitHub is optional because the cluster path does not use it. If you only ever remediate through Klaudia, there is nothing to connect. Configure the source path without a connection behind it and the agent refuses at validation rather than failing mid-run.
The wizard’s tool checklist has no effect here: the agent fixes its own tool surface in the implementation, so what it can do is decided there rather than by what you tick.

The approval boundary

This is the part worth understanding before deploying it. When Klaudia pauses for an approval, this agent cannot answer it. The tool that would respond is denied to it in its own code, so a gate Klaudia raises comes back to a human every time. That holds regardless of how the agent is configured or what its instructions say — it is not a setting that can be relaxed. See Approvals for where those decisions land.

Ask it for

It takes a completed investigation rather than a free-text instruction, so it is normally driven by a workflow step. Where you invoke it directly, pass the investigation to act on:

Defaults and limits

The time budget bounds this agent’s run, not the remediation. Work it has delegated to Klaudia, and any approval waiting on a person, continue past it.

In a workflow

It is the final step, downstream of an investigation and usually of a decision. A typical incident workflow investigates, asks Remediation whether a change is warranted, routes the proposal through an approval, and only then reaches here. Putting it directly after an investigation skips the step that decides whether anything should change at all — which is a choice, but worth making deliberately.

What it will not do

It cannot approve or reject on a person’s behalf, as above. It also does not decide what the fix should be. It carries out what an investigation established, through a system that has its own controls — so the guardrails on the live cluster are Klaudia’s, and the guardrail on the source is that a pull request still needs a reviewer.

Next steps

Remediation

Decide whether a change is warranted first.

Approvals

Where a paused decision lands, and who may answer it.

Klaudia Investigator

The same Klaudia, used to investigate rather than to act.

Agent catalog

Every catalog agent, side by side.