> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/product-updates-changelog/2025-q4/december-2025.md).

# December 2025

## Key Initiative Enhancements

* New Fields: Type (Product, Process, or Agent), Tracking Metric, and Performance to provide a granular view of your progress.
* Intuitive side-drawer: making it easier than ever to create and edit your Initiatives work.
* Smart Associations: Tailor your project structure by linking multiple opportunities to Product/Process initiatives, or associating specific Agents and Criteria to Agent-based tasks.
* Enhanced UX: Reference links now display favicons for instant recognition, and you can quickly view a team member's contact info by hovering over the owner or assignee fields.

## New Analytics Widgets

To help you gain deeper insights, we have added two powerful new chart types:

* Comparison Chart: Benchmarking is now effortless. Compare your current data against previous or specific time periods with a visual design that clearly distinguishes performance gaps.
* Multi-series Chart: For complex data storytelling, this chart allows you to visualize two metrics, two breakdowns, and two chart types simultaneously, complete with a configurable secondary Y-axis.


---

# 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://ask.birdie.ai/product-updates-changelog/2025-q4/december-2025.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.