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.

How it works?

To use Klaudia in Slack, you need a Komodor account and a Slack workspace. Connect them once by installing the Slack integration from your Komodor account (steps below). After that, any mention of @Komodor in that workspace will automatically identify the workspace and authorize users whose Slack email matches a user in that Komodor account.

What Klaudia can do in Slack

Capability Status
Investigation via @Komodor in channel ✅ Available
Private investigation via /komodor ✅ Available
DM with Klaudia bot (truly private) ✅ Available
Streaming RCA with inline tool steps ✅ Available
One-click remediation with confirmation ✅ Available
Channel context (user-initiated, bounded) ✅ Available
Deep links to Komodor UI for mentioned objects ✅ Available
Slack conversations visible in Klaudia UI history ✅ Available
Audit log with Slack source field ✅ Available
File analysis (logs, configs, screenshots) 🔜 Coming Soon
Multi-user thread participation (others can act) 🔜 Coming Soon
Proactive Klaudia-initiated alerts 🔜 Coming Soon
Cross-channel context 🔜 Coming Soon

Prerequisites

  • Beta feature flag enabled on your account - contact your Komodor CSM.
  • Your Slack workspace must be connected to a Komodor account via the Slack integration. 
  • You must have a Komodor account with an email that matches your Slack email. 
  • When you mention @Komodor, Klaudia identifies your workspace and authorizes you automatically based on that email match. 
  • If your email is not recognized in the connected Komodor account, Klaudia will reject the interaction.

Installation

Note: Existing Komodor slack users should uninstall first and then re-install it according to the following steps:

  1. Once logged into the Komodor platform click on the Integrations tab.
  2. Locate the integration for Slack under the Available Integrations section and click on Install Integration to start.

install_integration.png

Screenshot 2026-05-10 at 11.36.04.png

        3. You might be prompted to log in to your Slack workspace, 
             if so log in and and click Continue.

slack_step1.png

      4. Click on Allow to complete the integration for Slack.

Screenshot 2026-05-10 at 11.42.19.png

      5. Once completed you will be forwarded back to the Komodor Integration page 
          where you will find the Integration for Slack listed under the Installed Integrations.

      6. Each Slack user must link their Komodor account 
          before Klaudia returns any data.

Three ways to use Klaudia in Slack

  1. @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.
  2. /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.
  3. 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. 

The context 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.

Default context configuration:

Parameter Value Description
window_seconds 24h Lookback window for channel history
max_messages 50 Maximum number of channel messages to retrieve
per_message_chars 400 Maximum characters captured per message
total_chars_cap 15,000 Total character limit for the full extracted context
expand_threads 10 Maximum number of threads to expand
replies_per_thread 5 Maximum replies fetched per expanded thread
replies_concurrency 5 Number of concurrent requests for fetching thread replies

Permission model

Surface Visible to Who can interact
@Komodor in channel (thread) All channel members Thread initiator only (MVP)
/komodor in channel Invoking user only Invoking user only
DM DM user only DM user only

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.

Note: Only the user who initiated the thread or slash command can send follow-up messages. Other channel members can read the thread but cannot interact with Klaudia.

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.

Track connected users

  • Go to Integrations -> Click 'View Details' in the Slack integration card:
Screenshot 2026-05-25 at 18.42.38.png
  • Visible only to users with Klaudia.Manage permission (already established in your auth model).

Investigations History

  • View Klaudia investigations by their source of origin.

  • Click an investigation to open the Slack channel where it started.

Screenshot 2026-05-25 at 18.47.19.png

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.

 

 

 

 

 

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.