> ## Documentation Index > Fetch the complete documentation index at: https://docs.komodor.com/llms.txt > Use this file to discover all available pages before exploring further. # Remediation > Reads a finished investigation and returns a typed decision — propose a fix, decide no action is warranted, or ask the questions that would settle it. Deploy this agent to put a deliberate step between an investigation and an action. It consumes a completed investigation from any domain and decides what should happen about it, without touching anything itself. This page covers what it takes as input, the three answers it can give, and where it stops. ## What it does You hand it a finished investigation. It reads the findings and the run transcripts behind them — separating what was actually observed from what was inferred — and returns one of three typed decisions: | Decision | When it returns this | | ------------------- | ------------------------------------------------------- | | A proposed remedy | The evidence supports a specific fix | | No action warranted | The finding does not justify changing anything | | Questions | Something is missing, and it names what would settle it | Reading the transcripts rather than only the summary is the point. A confident-sounding finding built on an inference is a different thing to act on than one built on an observation, and the distinction survives into its decision. ## What it reads | Source | What it uses it for | | ----------------------------------- | ------------------------------------------- | | The investigation's findings | What was concluded | | The investigation's run transcripts | What was actually observed, versus inferred | It holds no cloud, cluster or repository credentials, and has no shell. Its only reach is back into the platform for the investigation it was given. ## Before you deploy | Requirement | Detail | Where to set it up | | ------------ | ----------------------------------------------------- | ---------------------------------------------------------------------- | | Model access | The managed model gateway, or your own Claude API key | [Credentials & secrets](/manage-your-agents/build/credentials-secrets) | There is nothing else to connect. Because it is plan-only, there is no integration to bind and no credential for a target system — which is also why it deploys to either target equally: there is nothing private for a self-hosted deploy to unlock. ## Ask it for It takes a completed investigation rather than a free-text question, so it is normally driven by a workflow step rather than by a person. Where you do invoke it directly, pass the investigation you want a decision on: ```text theme={null} Take the AWS investigation from run 4f2a and tell me whether it justifies a change. If it does, propose one. If the evidence is not there, say what would settle it. ``` ## Defaults and limits | | | | ----------- | ------------------------------------------ | | Catalog ID | `remediation` | | Model | `claude-sonnet-5` | | Time budget | 300 seconds, adjustable 60–900 per run | | Deployment | Komodor cloud or self-hosted | | Chat | No — it consumes an investigation envelope | ## In a workflow It is the decision step between investigation and action. An incident workflow investigates, passes the result here, and routes on what comes back: a proposed remedy goes to an executor or to a human for approval, questions go back to the specialists that can answer them, and no-action closes the loop without a change. That routing is what makes the third answer useful. An agent that could only propose fixes would propose one for every finding. See [Orchestration](/manage-your-agents/run/orchestration) and [Approvals](/security-and-governance/controls/approvals). ## What it will not do It never mutates a live system. Not as a policy setting, and not as a prompt instruction — it has no credentials for a target system and no shell, so there is nothing to mutate with. A proposed remedy is a recommendation until something else carries it out. Its name invites the opposite assumption, which is worth stating plainly to anyone reviewing its access: this agent plans, and [Remediation Executor](/manage-your-agents/build/catalog/remediation-executor) is the one that acts. ## Next steps Carry a proposed remedy out. Put a human decision in front of an action. How a workflow routes on what this agent returns. Every catalog agent, side by side. ## Related topics - [Remediation Executor](/manage-your-agents/build/catalog/remediation-executor.md) - [CI/CD Health & Remediation](/modules-and-workflows/ops-automation/ci-cd-pipeline-health.md) - [Agent catalog](/manage-your-agents/build/catalog/overview.md) - [Incident management & troubleshooting](/modules-and-workflows/sre/incidents.md) - [Cloud Cost](/modules-and-workflows/cost-optimization/cloud-optimization.md)