Klaudia for Slack (Beta)

Overview

Klaudia is Komodor's AI SRE agent. With Klaudia for Slack, engineers can trigger cluster investigations, receive RCA summaries, and approve remediations — without switching to the Komodor UI. Klaudia is included in the same Komodor Slack app installation that handles monitor notifications.

Klaudia for Slack is currently in beta. A separate beta Slack app is used during this phase. Once the updated app passes Slack Marketplace review, customers will be able to migrate to the production app (reinstall required). To get Klaudia for slack, please contact our support team.

What Klaudia can do in Slack

Prerequisites

• Komodor Slack app installed in your workspace (see Integration for Slack)
• Beta feature flag enabled on your account - contact your Komodor CSM
• Each Slack user must link their Komodor account before Klaudia returns any data

Three ways to use Klaudia in Slack

@Komodor in a channel Mention @Komodor in any channel. Klaudia acknowledges immediately and opens a thread where the full investigation runs. The thread and its contents are visible to all members of the channel — this is a Slack platform constraint, not a Komodor setting. Only the thread initiator can send follow-up messages to Klaudia; other members can read results but cannot interact.

→ Use this when: you want your team to see the investigation in real time.

/komodor in a channel Klaudia responds ephemerally — the response is visible only to you and no thread is created. Other channel members do not see the interaction.

→ Use this when: you want to investigate without surfacing the output to the channel.

DM Klaudia directly Open a direct message with the Komodor app in Slack. 

→ Use this when: you need a fully private, persistent session.

Channel context

By default, Klaudia starts each investigation from the moment you mention her. She does not passively read channels.

To include prior channel messages as context, explicitly ask her at the start:

"@Komodor include the recent channel history as context — why is payments-api returning 500s?"

The lookback window is bounded to prevent overload. The exact limit is configurable — check with your Komodor admin or CSM for the value set on your account.

Remediation actions

Klaudia suggests remediations as action cards in the thread:

• No auto-execution — explicit confirmation always required
• Only the thread initiator can run actions (current MVP)
• Actions are scoped to the thread initiator's Komodor RBAC
• Unlinked users who attempt to run an action receive an ephemeral rejection message
• Every action executed via Slack is written to the Komodor audit log

Permission model

Klaudia's responses are always scoped to the invoking user's Komodor RBAC. Data the user is not authorized to see in Komodor is not surfaced in Slack.

Audit log

All Klaudia Slack actions are recorded in the Komodor audit log:

• Source: Slack (channel name included)
• Slack user who triggered the action
• Timestamp
• Action taken
• Triggered by: Klaudia or User (separate field)

Authorization events (account link, renewal, expiry) are logged and visible only to users with the Klaudia.Manage permission.

FAQ

Does Klaudia for Slack replace the existing monitor notifications? No. Monitor notifications continue exactly as before under the same Slack app.

Can Klaudia read my channel without being mentioned? No. Klaudia is passive until mentioned. Channel history is only ingested when you explicitly ask her to include it.

What happens to Slack conversations in Komodor? Slack investigations appear in Klaudia's conversation history in the Komodor UI. Clicking a Slack conversation opens the Slack thread directly. If you are not a member of the Slack channel where the conversation happened, you will see a message indicating you do not have access.