> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rubixkube.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What's new

> The highlights of what changed in RubixKube, newest first.

Here's what changed recently, newest first, and why you'd care. Some features need a plan: where that's so, the entry says **Business and Enterprise**.

## November 2026

### Slack

* **Incident threads.** Each new incident or group gets its own Slack thread. The first message follows the incident's status, and replies in the thread become comments on the incident. [Slack](https://docs.rubixkube.ai/integrations/slack.md). Business and Enterprise.
* **A channel per category.** Send Incidents, Reports, Account and Uptime messages to different channels from **Customize > Channels**. Anything you don't set goes with Incidents. [Slack](https://docs.rubixkube.ai/integrations/slack.md).
* **Cards in Slack.** RCAs, Tasks and artifacts now show as cards, so you can read the main points without leaving the thread. [Slack](https://docs.rubixkube.ai/integrations/slack.md).

## October 2026

### Incidents and RCAs

* **The journey on every incident.** The incident page shows each step from detection to report and how many minutes each took. It also says when the RCA starts and what it's waiting for. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Recovery you can see.** Rows and pages say **Recovered**, who closed the incident, and what fixed it. Answer **What fixed it?** yourself or ask Rubix to check. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Groups.** Incidents on the same resource or with the same cause share one group and one RCA, across sources. Closing a group closes its members. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Triage before the RCA.** Triage sets severity and impact, can hold an RCA, and can mark an alert as known. You spend less time on noise. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Known noise says so.** When earlier RCAs show an alert is expected, the incident tells you, with **Ignore** and **Run RCA again**. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Something broke, or works worse.** Incidents now carry an impact, and you can filter to degradations. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Problems that come back.** A closed incident that returns opens a new incident linked to the old one. You set how often Rubix investigates a repeat in **Settings > Incidents**. [Settings](https://docs.rubixkube.ai/using/settings.md).
* **Urgent RCAs go first.** The wait before an RCA depends on severity, and urgent work runs ahead of the rest. [Root cause analysis](https://docs.rubixkube.ai/concepts/root-cause-analysis.md).
* **Run RCA again.** Start it from the RCA page or a list row. It skips every automatic wait. [RCAs](https://docs.rubixkube.ai/using/rca-reports.md).
* **Clearer RCA reports.** Reports gained charts, citations, structured evidence, a **Full report** tab and **Export as Markdown**. **Was this the cause?** shows only when the report states a cause. [RCAs](https://docs.rubixkube.ai/using/rca-reports.md).
* **Short codes.** INC-12, RCA-4 and TSK-30 work everywhere, including Rubix and MCP. It's easier to say "look at INC-12". [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **Comments and mentions.** Tag people with @, and mention @Rubix to ask it something on the incident. Mentions reach people through the bell and email. [Incidents](https://docs.rubixkube.ai/using/incidents.md).
* **One toolbar for lists.** Incidents, RCAs, Tasks and My tasks now filter, sort and group the same way. [Tasks](https://docs.rubixkube.ai/using/tasks.md).

### Rubix

* **Rubix in the console.** Pin context with @, run commands with /, stop a reply partway, and see Rubix's work as quiet rows. Rubix can also make artifacts you can keep. [Chat with Rubix](https://docs.rubixkube.ai/using/rubix-chat-agent.md).
* **Modes.** Observe, Assist and Auto decide what Rubix can do on its own. An admin sets the default and the highest mode. [Modes](https://docs.rubixkube.ai/using/modes.md).
* **Response style.** Choose how much Rubix says while it works: Quiet, Normal or Verbose. [Modes](https://docs.rubixkube.ai/using/modes.md).
* **Commands, Agents and Hooks.** Turn common prompts into slash commands, add your own agents, and add your own checks before Rubix changes something. Hooks are for Business and Enterprise. [Customize](https://docs.rubixkube.ai/using/customize.md).

### Automations

* **The Automations page.** Build automations with a trigger and steps, then see them in Overview and Runs. **Try it** tests a draft before you publish. [Automations](https://docs.rubixkube.ai/using/automations.md). Business and Enterprise.
* **System built-ins.** The System tab shows what RubixKube runs for you. When a built-in has a newer version, you see **Update available**. [Automations](https://docs.rubixkube.ai/using/automations.md).

### Integrations and webhooks

* **Tools as sources.** Datadog, PagerDuty, Grafana, Sentry, Jira, Linear and Observe connect from **Environments** by webhook, and their alerts open incidents. Each source page shows its last messages. [Integrations overview](https://docs.rubixkube.ai/integrations/overview.md).
* **Your own webhooks.** Send events from your own tools from **Customize > Webhooks**. [Your own webhook](https://docs.rubixkube.ai/integrations/webhooks.md). Business and Enterprise.
* **See what a connection can read.** Each integration has a section showing what Rubix can read through it, so you know before an RCA needs it. [Integrations overview](https://docs.rubixkube.ai/integrations/overview.md).
* **Sign in the way each tool expects.** Connections now use each tool's own sign-in or token, so there's less to work out. [Sign-in and tokens](https://docs.rubixkube.ai/integrations/oauth-and-auth-types.md).
* **Custom MCP servers.** Add your own MCP servers. [Custom MCP servers](https://docs.rubixkube.ai/integrations/custom-mcp-servers.md). Business and Enterprise.

### Slack

* **Slack answers from Rubix.** Mention Rubix in a channel and you get the same agent as in the console. [Slack](https://docs.rubixkube.ai/integrations/slack.md).

### MCP

* **The RubixKube MCP server.** Read and update incidents, RCAs and Tasks from Claude Code, Cursor, VS Code and Claude. You sign in as yourself, and what you do is recorded under your name. [MCP](https://docs.rubixkube.ai/integrations/mcp.md).
* **Knowledge tools.** Your AI tool can search past incidents, find similar ones and ask what changed. [MCP](https://docs.rubixkube.ai/integrations/mcp.md).

### Sources and observers

* **Environments are labels.** A source is a cluster, cloud account, machine or tool. An environment, such as staging, is a label across sources, and you can filter by it. [Environments](https://docs.rubixkube.ai/concepts/environments.md).
* **One page for every source.** Each source shows what's happening right now and what changed. [Environments](https://docs.rubixkube.ai/using/environments.md).
* **Links between sources.** Rubix asks whether two sources are the same thing, and you answer Yes, No or Skip. [Environments](https://docs.rubixkube.ai/using/environments.md).
* **Observer settings in the console.** Change timings, watch lists and rule values, and test a query rule, without touching the install. [Observers](https://docs.rubixkube.ai/concepts/observer-agent.md).
* **Early recovery and more pods.** Observers report recovery sooner, and large clusters can run more than one observer pod. [Kubernetes](https://docs.rubixkube.ai/environments/kubernetes.md).

### Analytics

* **Five numbers.** Mean time to understand, Coverage, Noise removal, Speed and Accuracy, with a summary on top and a report you can download as a PDF. [Analytics](https://docs.rubixkube.ai/using/analytics.md).
* **A better weekly digest.** The email leads with what Rubix worked on and links to Analytics. [Notifications](https://docs.rubixkube.ai/using/notifications.md).

### Settings

* **Models.** Add your own providers, and set the Primary and Worker models for your organization. Each chat can pick its own model. [Models](https://docs.rubixkube.ai/using/models.md). Own providers are for Business and Enterprise.
* **Usage and plan.** See your limits and how much of each you've used, with AI token usage. [Usage and plan](https://docs.rubixkube.ai/using/usage-and-plan.md).
* **Activity.** Filter, page through and export the record of what happened in your organization. Admins only. [Settings](https://docs.rubixkube.ai/using/settings.md).
* **Many organizations.** One person can belong to several organizations and switch between them. Sign-up now asks you to name yours, and invites join you directly. [Members](https://docs.rubixkube.ai/using/members.md).

> [card] [Quickstart](https://docs.rubixkube.ai/getting-started/quickstart.md)
>
> New here? Start with this.

> [card] [Integrations overview](https://docs.rubixkube.ai/integrations/overview.md)
>
> See everything you can connect.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.