Kilo Code incident

Update to Kilo Bot for Slack Degraded

Resolved on August 9, 2026, affecting Kilo Bot.

resolved Aug 09, 2026, 03:02 PM UTC

We were affected by the recent security incident at Metabase. For more details about the Metabase incident, please see this post on the Anaconda blog: https://www.anaconda.com/metabase-incident-impacting-kilo-code-customer-data As a result of our investigation, all Kilo Slackbot instances were deactivated and the small subset of Kilo-Slack users were notified to reauthenticate. For more information on reactivating Kilo Slackbot, please see the documentation: https://kilo.ai/docs/code-with-ai/platforms/slack#setup

Started
Aug 09, 2026, 03:02 PM UTC
Resolved
Aug 09, 2026, 03:02 PM UTC
Duration
–
Detected by Pingoru
Aug 09, 2026, 03:02 PM UTC

Affected components

Kilo Bot

Update timeline

  1. resolved Aug 09, 2026, 03:02 PM UTC

    We were affected by the recent security incident at Metabase. For more details about the Metabase incident, please see this post on the Anaconda blog: https://www.anaconda.com/metabase-incident-impacting-kilo-code-customer-data As a result of our investigation, all Kilo Slackbot instances were deactivated and the small subset of Kilo-Slack users were notified to reauthenticate. For more information on reactivating Kilo Slackbot, please see the documentation: https://kilo.ai/docs/code-with-ai/platforms/slack#setup

Your product runs on more than Kilo Code

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →