> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/changelog/readme/2025-12.md). # December 2025 5 product updates shipped in December 2025. See [Product Updates](/changelog/readme.md) for the latest. {% updates format="full" %} {% update date="2025-12-14" %} ## Export CSV for App Ratings #### What's new? * You can now export App Ratings survey results as a CSV file, with results delivered directly to your email. * This follows the same export behavior already available for NPS and Custom Surveys. #### Why this matters? * Easily export and analyze your App Ratings data outside the dashboard without needing to request manual data exports. #### Availability * Available under In-App Surveys > App Ratings Survey Results > Export CSV. {% endupdate %} {% update date="2025-12-09" %} ## MCP Server: 10 Tools Organized by Debugging Workflows #### What's new? * The MCP Server now includes 10 tools, organized around the real questions you ask while debugging: * App context: quickly understand which app you are working with. * Crash analysis: access crash groups, detailed crash data, and pattern insights. * Occurrence-level context: view device info, OS, logs, and user details for any occurrence. * App hang visibility: identify and investigate app hangs across platforms. * Bug and review correlation: connect SDK-reported bugs and store reviews back to stability data. #### Why this matters? * Instead of navigating a flat list of API tools, you can find exactly what you need based on the debugging question you are trying to answer, making the MCP Server more intuitive and productive. {% endupdate %} {% update date="2025-12-08" %} ## AI-Powered PR Review #### What's new? * A new AI-powered PR Review feature is now available. Once enabled, you can mention Luciq in any GitHub pull request to get an automated review. * Luciq analyzes the PR, detects potential bugs or issues, and recommends fixes directly in the PR comments. * To use it, connect your code repository under Settings > Source Code Management and enable PR Review. #### Why this matters? * Catch bugs and issues earlier in the development cycle. AI-powered reviews help your team ship more stable code by surfacing problems before they reach production. {% hint style="info" %} ### Note Interested in trying this out? Please reach out to our support team or your Customer Success Manager to enable it for you. {% endhint %} {% endupdate %} {% update date="2025-12-08" %} ## OAuth for MCP Server #### What's new? * OAuth authentication is now available for the MCP Server, replacing the need for manual token generation. * Authenticate directly through the Dashboard under Luciq MCP > Connect. * For existing MCP users, previously generated tokens continue to work. You can optionally switch to OAuth by reconnecting. * New users can get started with OAuth right out of the box. #### Why this matters? * Getting started with the MCP Server is now easier and more secure. OAuth removes the extra step of generating and managing tokens, so you can connect your IDE to Luciq faster. {% endupdate %} {% update date="2025-12-01" %} ## GitHub Integration for Dynamic Team Ownership #### What's new? * You can now integrate with GitHub via Source Code Management to fetch your CODEOWNERS file and automatically assign crash ownership to the right teams. * The integration can be used for both the Resolve Agent and CODEOWNERS-based team ownership, or just one of the two. #### Why this matters? * Crash ownership is automatically kept in sync with your existing CODEOWNERS file, so the right team is notified without any manual configuration on the Luciq side. {% endupdate %} {% endupdates %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.luciq.ai/changelog/readme/2025-12.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.