> ## 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.

# What's new

> Where release notes live, how to read them, and how to keep track of what changed in your own workspace.

The Komodor Agentic Operation Platform (KAOP) ships continuously, so its release notes live inside the
product rather than in this documentation. This page explains where to find them, what each entry
tells you, and how to tell whether a change has reached your workspace yet.

## Where the release notes live

Open **What's new** from the left navigation, or go straight to `/whats-new` in your workspace. The
page is titled **Recently shipped** and presents a newest-first timeline of user-visible features,
improvements, and fixes.

Because the feed is served by the environment you are signed in to, it describes what is actually
running for your workspace — not a general release history you then have to reconcile against your
own account.

## Reading an entry

Every entry carries a ship date, a category chip, a short plain-language summary, and often a
screenshot.

| Chip         | What it means                                       |
| ------------ | --------------------------------------------------- |
| **New**      | A capability that did not exist before.             |
| **Improved** | An existing capability that changed for the better. |
| **Fixed**    | A defect that is now resolved.                      |

Where an entry maps to a specific screen, it carries a **Try it** button that takes you straight
there — so reading about a change and using it are one step apart.

<Note>
  The feed is curated rather than exhaustive. It covers changes a KAOP operator would want to know
  about, not internal refactors or invisible fixes.
</Note>

## Tracking what you have not seen

The **What's new** navigation entry shows a count of entries published since your last visit, and
opening the page clears it. The marker is stored in your browser, so it is per-person and
per-browser rather than per-workspace — a teammate's unread count is their own.

## Keeping up deliberately

<Steps>
  <Step title="Check the feed after an upgrade window">
    Open **Recently shipped** and read down to the last date you remember. The category chips make
    it quick to separate new capabilities from fixes.
  </Step>

  <Step title="Confirm the change in your own workspace">
    Follow the entry's **Try it** link. If the screen behaves as the entry describes, the change is
    live for you.
  </Step>

  <Step title="Check module enablement for anything you cannot find">
    Some capabilities are enabled per workspace. If an entry describes a surface you do not see,
    open [Modules → Overview](/modules-and-workflows/overview) and check whether the module that
    owns it is turned on.
  </Step>
</Steps>

## When the docs and the product disagree

These pages track the product. If you find a page that describes behavior you do not see, treat the
product as correct and tell us — see [Support](/reference/support).

## Next steps

<CardGroup cols={2}>
  <Card title="Support" href="/reference/support">
    How to reach the Komodor team and what to include.
  </Card>

  <Card title="Modules overview" href="/modules-and-workflows/overview">
    Which modules are enabled for your workspace, and what is available to turn on.
  </Card>

  <Card title="Troubleshooting" href="/reference/troubleshooting">
    Common problems and their fixes.
  </Card>

  <Card title="Limits & quotas" href="/reference/limits-quotas">
    The caps that apply to a workspace.
  </Card>
</CardGroup>


## Related topics

- [Support](/reference/support.md)
- [Agent spend attribution](/manage-your-agents/optimize/agent-spend-attribution.md)
- [Skills](/manage-your-agents/build/skills.md)
- [Credentials & secrets](/manage-your-agents/build/credentials-secrets.md)
- [Cloud Cost](/modules-and-workflows/cost-optimization/cloud-optimization.md)