> 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.md). # Product Updates {% updates format="full" %} {% update date="2026-08-05" tags="no-sdk-update-required" %} ## Luciq Agent: your in-dashboard AI assistant is now in beta #### What's new? * **A conversational AI assistant now lives inside the Luciq dashboard.** Click the sparkle icon in the header and ask anything about your app in plain English. * **Every Luciq product, one conversation.** Crashes, APM, bug reports, hangs, reviews, surveys, opportunities, alerts, and app health, all in the same thread. * **Grounded in your live data.** Every response is a real query against your account, using the same permissions as your dashboard user. * **Context-aware.** The agent picks up which app and environment you're on from the page you're viewing, so you don't have to spell it out. * **Investigate, then act.** The agent can take actions on your data, and every write pauses for your explicit approval before it runs. #### Why this matters? * Skip the dashboard hunt. No more opening three tabs, filtering menus, or exporting to find an answer. * Multi-product synthesis in one thread. Ask *"which crashes are showing up in our 1-star reviews?"* and get the answer, not just a description of how to look it up. * Follow-ups keep context, so you can refine or pivot topics without restarting. #### Availability * In beta, enabled for every enterprise account. * No SDK update required. * Contact your Customer Success Manager or Luciq Support if you don't see it in your dashboard. Documentation {% endupdate %} {% update date="2026-08-05" tags="no-sdk-update-required" %} ## MCP: drill into AI-detected issues and their screenshots #### What's new? * Two new Luciq MCP tools for AI-detected issues: **`ai_issue_details`** returns the group summary and a paginated occurrence history for a single `visual_issue` or `broken_functionality` issue, and **`ai_issue_occurrence_details`** returns one occurrence's full context together with its screenshots. * Use the `id` and `issue_type` of an AI-detected issue surfaced by `list_issues` to pull its details, then an occurrence's `number` to fetch that occurrence's screenshots. #### Why this matters? * Previously, `list_issues` could surface an AI-detected issue but your agent had no way to inspect it further from MCP. Now it can pull the full occurrence history and see the actual screenshots without leaving your IDE. Documentation {% endupdate %} {% update date="2026-08-05" tags="no-sdk-update-required" %} ## Bug Grouping: sharper AI summaries that refresh as a group grows #### What's new? * Group AI summaries now reflect the same signals your grouping logic uses: when Bug Grouping considers **Network Logs** and **User Steps**, those are factored into the summary alongside the report titles. * Summaries regenerate automatically as a group grows — refreshed when the group reaches **3 duplicates**, and again at **7 duplicates**. * Each refresh considers **all** duplicates in the group, including manually-marked ones, rather than a truncated batch. #### Why this matters? * Understand a whole group at a glance without opening each duplicate. * A group with 20+ duplicates reflects the full pattern, not just the first report that created it. * Summaries carry real technical signals, not just titles, so they point closer to the root cause and speed up triage. #### Availability * Enabled by default on top of existing Bug Grouping. No SDK update required. * Applies going forward: only groups that gain new duplicates after the release get the refreshed summary, and existing groups are not backfilled. Only automatic grouping triggers re-summarization, and a group's **title** is set once and stays fixed while the summary regenerates. Documentation {% endupdate %} {% update date="2026-08-04" tags="no-sdk-update-required" %} ## Opportunities now learn from your In-App Surveys #### What's new? * **Survey responses are now a third source for Opportunities**, alongside bug reports and app store reviews, with no extra setup as long as Opportunities is enabled. * Similar requests from survey responses are grouped into themes across questions and surveys, so a single Opportunity can be backed by evidence from multiple surveys at once, together with other sources like Bug Reporting and App Reviews. * The **Sources** panel shows which survey and question drove the Opportunity and links back to the survey, the same as it already does for bugs and reviews. #### Why this matters? * Your surveys feed directly into the "what should we build next?" list, with no manual stitching across products. #### Availability * Available for customers on **production** for now. Single-tenant customers need to reach out first. * Picks up going forward only: responses collected from now on are included, with no backfill of older surveys. Documentation {% endupdate %} {% update date="2026-08-03" tags="no-sdk-update-required" %} ## Per-user debugging and session replay in Luciq MCP #### What's new? * Two new Luciq MCP tools: **`user_summary`** and **`list_session_replays`**. * `user_summary` returns one end user's devices, OS and app versions, sessions, per-metric APM occurrences by Apdex class, and the crashes and bugs they hit, all in a single call. * `list_session_replays` lists recorded sessions for an app, newest first, with a dashboard deep link on every row. It's also the only MCP tool that can look a user up by email. * Several existing tools (`list_crashes`, `list_app_hangs`, `list_bugs`, `list_occurrences_tokens`, `apm_list_groups`, `apm_group_view`, `apm_occurrence`) can now filter by specific user IDs. #### Why this matters? * Support and engineering can go from "a user reported X" to that person's full picture, devices, performance, crashes, and bugs, without leaving the IDE or chaining several separate queries. #### Availability * Available to all Luciq MCP users. `user_summary` requires the APM plan feature and `list_session_replays` requires the Session Replay plan feature. Documentation {% endupdate %} {% update date="2026-08-02" tags="no-sdk-update-required" %} ## Funnel steps now support OR-grouped events #### What's new? * The `apm_funnel_write` MCP tool takes an ordered `steps` array, and each step is an OR group of up to 5 events. A session completes the step as soon as **any** of that step's events occurs. #### Why this matters? * Funnels can model steps with more than one valid path, for example an "add to cart" step that counts whether it happened from the product page or the cart drawer, without splitting them into separate funnels. Documentation {% endupdate %} {% endupdates %} *** ## Earlier updates * [July 2026](/changelog/readme/2026-07.md) * [June 2026](/changelog/readme/2026-06.md) * [May 2026](/changelog/readme/2026-05.md) * [April 2026](/changelog/readme/2026-04.md) * [March 2026](/changelog/readme/2026-03.md) * [February 2026](/changelog/readme/2026-02.md) * [January 2026](/changelog/readme/2026-01.md) * [December 2025](/changelog/readme/2025-12.md) * [November 2025](/changelog/readme/2025-11.md) * [October 2025](/changelog/readme/2025-10.md) --- # 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.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.