> 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-07.md).
# July 2026
11 product updates shipped in July 2026. See [Product Updates](/changelog/readme.md) for the latest.
{% updates format="full" %}
{% update date="2026-07-30" tags="no-sdk-update-required" %}
## Dashboard Timezone Support
#### What's new?
* You can now select your preferred timezone in your **Profile settings**. The dashboard defaults to **UTC** until a custom timezone is set.
* Charts, timestamps, and date range filters across APM, crashes, incidents, releases, sessions, and screens now instantly localize to your chosen timezone.
* Timezones are fully aware of Daylight Saving Time (DST) rules and will accurately display the correct abbreviation (e.g., `(UTC+03:00) Africa/Cairo (EEST)`).
* When sharing URLs or filters, the data remains synchronized to the exact moment in time, seamlessly adapting to the recipient's local timezone settings.
#### Why this matters?
* Distributed teams can now view crash reports, session replays, and performance metrics localized exactly to their own local time. This eliminates mental timezone math during triage and makes cross-team collaboration much more intuitive.
#### Availability
* Available immediately across the Luciq dashboard.
Documentation
{% endupdate %}
{% update date="2026-07-29" tags="no-sdk-update-required" %}
## Visual Issues are now grouped by similarity
#### What's new?
* Visual issues that describe the same underlying defect are now collected into a **single group** with a count of the occurrences it holds, so a defect appearing across many sessions reads as one item instead of a run of near-identical entries.
* Grouping is based on what the issue actually describes: the defect itself, its likely root cause, and the flow the user was in when it was captured.
* **Sort by occurrences** to bring the most widespread issues to the top, both on the AI Issues page and in the Issues List on your Inbox, where a grouped issue shows a **Group** count.
* Open a group's **occurrences drawer** to inspect any single occurrence, with the exact screenshot and the session behind it, so you can still see what went wrong for one specific user.
* If an occurrence doesn't belong in a group, select it and **ungroup** it. You'll be asked why, and that answer is used to improve grouping accuracy.
#### Why this matters?
Repeat detections were the main thing standing between visual issues and a queue you can actually work through. Grouping collapses them, so the defects hitting the most users surface first and you stop reading past the same problem twenty times. The per-occurrence view stays available whenever you need one user's experience rather than the pattern.
#### Availability
* Available to enterprise customers with Detect Agent enabled.
Documentation
{% endupdate %}
{% update date="2026-07-29" tags="no-sdk-update-required" %}
## Filter bugs by whether they have a description
#### What's new?
* A new **Description** filter is available in the bugs list, under the **More** menu, with two options: **With description** (bugs that have a description) and **Without description** (bugs submitted with no description).
* A bug's description is its report title, so the filter surfaces the bugs that have one versus those that don't. It works across both new and existing bugs.
#### Why this matters?
* Separate described reports from empty ones during triage in a single click, instead of scanning the list by hand.
#### Availability
* Available now for all customers, with no setup needed.
{% endupdate %}
{% update date="2026-07-22" tags="no-sdk-update-required" %}
## Linear integration, with two-way sync
#### What's new?
* **The Linear integration is now live on your dashboard.** Forward bug reports, crashes, and APM alerts from Luciq to Linear — manually with a click, or automatically through your alerts and rules, exactly like the Jira integration.
* **Two-way sync is included.** Status changes on the Linear issue are reflected on the matching report in Luciq, and priority stays in sync in both directions.
* Each Linear workspace connects once through OAuth 2.0 on the **Shared credentials** page, and that connection is reused across all your apps.
#### Why this matters?
Issues reach your team where the work already happens, and stay accurate once they're there. Closing an issue in Linear resolves the report in Luciq, so neither side drifts out of date and nobody re-triages something that's already fixed.
Documentation
{% endupdate %}
{% update date="2026-07-20" tags="no-sdk-update-required" %}
## Control Bug Grouping from your dashboard
#### What's new?
* You can now enable or disable Bug Grouping and control its logic directly from your app settings page, with no need to reach out to us.
* From the dashboard you can enable or disable Bug Grouping (and give your consent directly, without contacting support), enable or disable **Network logs** in the grouping logic, and enable or disable **User Steps** in the grouping logic.
#### Why this matters?
* You're in full control of Bug Grouping and its logic from the dashboard, so you can turn it on and tune what it groups on without waiting on a support request.
#### Availability
* Available now for all customers.
Documentation
{% endupdate %}
{% update date="2026-07-15" tags="no-sdk-update-required" %}
## Bug Grouping: see metadata patterns across a group
#### What's new?
* A new **Group Patterns** section surfaces the common metadata patterns across the duplicates of a bug group.
* As in Crash Reporting, you can see patterns across app version, devices, OS version, current view, and feature requests.
#### Why this matters?
* Spot the potential root causes of a grouped bug at a glance, without opening every duplicate in the group.
#### Availability
* Available now for all customers, enabled by default on top of Bug Grouping. No SDK update required.
Documentation
{% endupdate %}
{% update date="2026-07-13" tags="no-sdk-update-required" %}
## Ask Luciq MCP about the docs
#### What's new?
* Luciq MCP can now answer documentation questions directly. Two new tools, **`search_documentation`** and **`get_documentation_page`**, give your AI agent a reliable, repeatable way to search and fetch content from the published Luciq documentation (docs.luciq.ai).
* Use `search_documentation` to find relevant guides, API references, or setup steps, then `get_documentation_page` to pull a matched page's full content.
#### Why this matters?
Previously, the MCP server only exposed observability data (crashes, bugs, performance, and so on). Now, whenever your agent needs something from the docs, it can retrieve the right page reliably and ground its answer in the current published docs, instead of scouring the site or relying on potentially outdated training data.
Documentation
{% endupdate %}
{% update date="2026-07-13" tags="no-sdk-update-required" %}
## Manage your alerts and rules with your AI agent
#### What's new?
* **Alerts & Rules management is now live on the Luciq MCP Server.** Your AI agent can read, create, update, enable, disable, and delete alert rules, and resolve or reopen triggered alerts — all through natural language, respecting your workspace's role-based permissions.
* Two new use-case skills help agents put this to work:
* [**Reducing alerting noise**](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-alert-noise) — finds the rules that fire too often to be useful and tunes them at the source, without weakening safety-critical coverage.
* [**Addressing alerting gaps**](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-alert-gaps) — cross-references current app health against your existing rules and proposes alerts only for metrics that are both unhealthy and unmonitored.
* Every change is presented as a plan for your approval before anything is written.
#### Why this matters?
Alert hygiene is tedious to do by hand across every metric and app — so noisy rules pile up and real gaps go unnoticed. Handing it to your agent means chatty alerts get tuned down and coverage gaps get filled, grounded in your actual Luciq data rather than guesswork.
Documentation
{% endupdate %}
{% update date="2026-07-12" tags="no-sdk-update-required" %}
## MCP: filter crashes by custom user attributes
#### What's new?
* The `list_crashes` MCP tool now accepts a **user attributes** filter, so an agent can scope a crash list to a specific segment of your users at query time.
* User attributes are the custom key/value parameters your app reports through the SDK (for example plan tier, industry, country, or tenant). You can now filter on them straight from your IDE, the same way you would on the dashboard.
* Match exact or partial values, and combine conditions across attributes to narrow to precisely the slice you care about.
#### Why this matters?
* For multi-tenant apps, you can pin down exactly which tenant or customer segment is hitting a crash instead of reading across the whole user base.
* Triage gets faster: ask for the crashes affecting one plan, region, or cohort and get just those back, without pulling everything and filtering afterward.
{% endupdate %}
{% update date="2026-07-12" tags="no-sdk-update-required" %}
## Luciq CLI: your app data and symbol uploads, from the terminal
#### What's new?
* A unified command-line interface for Luciq. Install it with `gem install luciq-cli` (or `brew install luciqai/tap/luciq-cli`) and authenticate with a personal token generated from **Account Management > Luciq CLI**.
* **Symbol uploads for every platform.** One tool uploads iOS dSYMs, Android ProGuard/R8 mappings, NDK `.so` files, React Native source maps, and Flutter Dart symbols — built for CI pipelines.
* **Query your production data.** Crashes, app hangs, bugs, APM metrics, reviews, surveys, app-health insights, and the unified Issues & Opportunities surface — printed as JSON that pipes straight into `jq` and scripts.
* **Manage your workspace.** Triage bugs, create and update alert rules, resolve triggered alerts, and manage APM funnels.
* Data commands run the same tools that power the Luciq MCP Server, with the same role-based permissions.
#### Why this matters?
Dashboards are great for exploring; terminals are great for automating. The CLI turns everything you can see in Luciq into scriptable commands, so symbol uploads live in your release pipeline and app-health checks live in your cron jobs — no custom API glue required.
Documentation
{% endupdate %}
{% update date="2026-07-06" tags="no-sdk-update-required" %}
## Consolidate your bug list with the `luciq-group-bugs` skill
#### What's new?
* A new agent skill, `luciq-group-bugs`, consolidates a noisy bug list by marking duplicates according to **your own** grouping logic, straight from your agent, with no dashboard clicking.
* Describe a rule in plain language and the skill fetches a scoped set of bugs, compiles your rule into an explainable grouping key per bug, and shows a dry-run plan of exactly which bug merges into which master before anything is written.
* Group by any combination of the same title, category, screen, tag, app version, user attribute, failed network request, or user steps.
* Because marking a duplicate is destructive, the skill always proposes the plan, shows the key behind every group, waits for your approval, and only then writes, with a one-session undo (detach only, or detach and restore status and priority).
#### Why this matters?
* Clean up a duplicate-heavy bug list on your own terms without clicking through the dashboard, with a safe approve-before-write flow that never merges anything you didn't sign off on.
Documentation
{% 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-07.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.