> 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-11.md). # November 2025 4 product updates shipped in November 2025. See [Product Updates](/changelog/readme.md) for the latest. {% updates format="full" %} {% update date="2025-11-20" %} ## Report Bugs from AI-Detected Issues #### What's new? * If you have AI-detected issues enabled (Visual Issues and Broken Functionality), you can now report a bug directly from any AI-detected issue. * Bugs reported this way are automatically labeled as AI issues in the bug reporting list for easy identification. #### Why this matters? * Streamlines the workflow from AI-detected issue to actionable bug report, so your team can triage and fix problems faster without switching between different tools or manually re-entering information. {% endupdate %} {% update date="2025-11-19" %} ## One Code Apps Support for Surveys, Issues, and Session Replay #### What's new? * If you use a shared codebase across multiple apps (one code apps), you can now: * Target surveys to a specific app using bundle ID. * Filter the issues list by bundle ID. * Filter Session Replay recordings by bundle ID. #### Why this matters? * Teams with shared codebases can now isolate data per app across surveys, issues, and session replays, making it easier to analyze and act on feedback and bugs for each app individually. {% endupdate %} {% update date="2025-11-17" %} ## Self-Serve Token Generation for MCP Server #### What's new? * You can now generate authentication tokens for the MCP Server directly from the dashboard, under Account Management > Luciq MCP. * The page provides the token and the JSON configuration script needed to connect to the MCP server. * Each token is per user and works across all AI clients (e.g., a single token works for both Claude and Cursor). #### Why this matters? * No more waiting on support to get set up with the MCP Server. You can generate tokens and start using the integration on your own, right from the dashboard. {% 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-11-04" %} ## Luciq MCP Server Launch #### What's new? * The Luciq MCP Server is now live. Tools like Cursor, Claude Code, and Copilot can connect directly to Luciq. * Developers can pull crash data, triage issues, and debug right from their IDE without switching to the dashboard. * Ask questions about crashes, crash details, and patterns and start debugging right away in the IDE. #### Why this matters? * No more copying stack traces from the dashboard and pasting them into your IDE or AI assistant. Luciq now has a seat inside your development environment, making debugging faster and more seamless. {% 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-11.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.