> 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/2026-01.md).
# January 2026
6 product updates shipped in January 2026. See [Product Updates](/changelog/readme.md) for the latest.
{% updates format="full" %}
{% update date="2026-01-26" tags="product-update,no-sdk-update-required" %}
## Session Insights \[Detect Agent] is now available in Session Replay
#### **What’s new?**
* Session Insights is now available in production 
* It provides you with the insights of a specific session
#### Why this matters?
* Understanding session context typically requires digging through timelines, screenshots, and logs, which can be time-consuming for customers.
* Session Insights summarizes the user’s actions and experience in a few seconds, helping teams understand what happened in a session much faster.
#### Availability:
* Available now and released to all Self-serve customers
* Available for Enterprise customers upon request
{% 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. Note that when enabled, we send the end-user report descriptions to a third-party LLM (data is not used for training).
{% endhint %}
{% endupdate %}
{% update date="2026-01-21" %}
## Video-Like Replay in Session Replay
#### What's new?
* Session Replay now supports video-like playback by capturing screenshots at higher frequency, creating a smoother replay experience.
* You can control when screenshots are captured: on navigation, on navigation and interaction, or at a set frequency.
* You can also adjust screenshot quality (High, Normal, or Black & White) to balance detail with storage.
* A size limit of 1 MB worth of screenshots per session applies. Lowering screenshot quality allows more screenshots to be captured within that budget.
#### Why this matters?
* Reviewing session replays now feels more like watching a video, making it easier to follow user flows and identify issues without gaps in the visual timeline.
#### Availability
* Android SDK v19.1.0+ and iOS SDK v19.2.0+.
{% endupdate %}
{% update date="2026-01-15" %}
## WebViews Support for iOS and Android
#### What's new?
* User Steps and Repro Steps now capture interactions inside WebViews for Bug Reports, Crash Reports, and Session Replay.
* Network requests happening within WebViews are now tracked in Network Logs.
* Screenshots now include WebView content in all reports.
#### Why this matters?
* Many apps rely on WebViews for critical flows like login, checkout, or account setup. Previously, these were blind spots in debugging. With this update, you get full visibility into what happens inside WebViews, just like native screens.
#### Availability
* iOS and Android SDK v19.2.0+. Both platforms require opt-in via SDK APIs. WebView masking is enabled by default for privacy.
{% 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="2026-01-14" tags="product-update,no-sdk-update-required" %}
## Bug Grouping \[Beta]
**What’s new?**
* Bug Grouping is now released in Beta 
* The feature automatically groups duplicate bugs using AI.
#### Why this matters?
* It removes the high, unnecessary friction developers face when manually marking duplicate bugs.
{% 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. Note that when enabled, we send the end-user report descriptions to a third-party LLM (data is not used for training).
{% endhint %}
Check Documentation
{% endupdate %}
{% update date="2026-01-12" %}
## Free-Typing User Events in Survey Targeting
#### What's new?
* When configuring survey targeting, you can now free-type exact user event names if the event you need is not visible in the dropdown.
* This works across all survey types that support event-based targeting.
#### Why this matters?
* If your app has a large number of user events (beyond the 400 shown in the dropdown) or uses SDK-defined events that were not previously surfacing, you can now target any of them by simply typing the event name.
{% endupdate %}
{% update date="2026-01-06" %}
## AI-Detected Issues: New Dedicated Page
#### What's new?
* A new dedicated page for AI-detected issues is now available, letting you browse "Visual Issues" and "Broken Functionality" in separate, organized lists.
* Each issue includes a description, screenshots, and a quick action to report it as a bug directly from the page.
* A new entry point from the Session Replay list gives you quick access to all AI-detected issues across your sessions.
#### Why this matters?
* You no longer need to open each session individually to find AI-detected issues. This page gives you a consolidated view of all detected issues across sessions, saving significant time during triage.
{% 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/2026-01.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.