> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/changelog/readme.md).

# Podigee changelog

Read customer-facing updates to Podigee products and supported integrations.

This section tells you about changes to Podigee. Each update states what changed, who is affected, what to do, and where to find the full instructions.

Read [Changes that may require action, October and November 2026](https://docs.podigee.com/changelog/action-needed/changes-that-can-need-your-action-october-and-november-2026.md) first. It tells you which changes affect your show and what to do.

The other groups are:

* **Podigee workspace:** the new interface, the Recording Studio, and Amplify.
* **Video and distribution:** video podcasts and the web player.
* **Analytics:** the figures of your shows.
* **Plans, accounts, and teams:** imports, teams, and private shows.
* **Feeds and episodes:** feed tags and show notes.
* **AI agents:** AI assistants and the Model Context Protocol (MCP) server.
* **Monetization:** the Podigee Audio Video Ad Server.
* **2025:** the main changes of 2025.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.podigee.com/changelog/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
