Issue Clusters

Repeated problems, not isolated noise.

Each cluster links back to public signals and produces a ticket that explicitly says the issue is reported, not internally verified.

Repeated Problems

Sorted by severity and evidence count.

26 live signals not yet matched to a cluster — review in the inbox.

Cluster detail

App quits mid-interview and returns wrong answers from screen context

Public signal includes the app exiting during live interviews and returning wrong or generic answers from screenshot context. A crash at the one moment the product is being trusted — a real interview or meeting — is a severity-one event, and should be tracked apart from generic UX gripes and from answer-quality regressions.

Needs retestcritical82% evidence strength

First seen

2026-02-21

Last seen

2026-05-22

Owner

engineering/ai

Status

Open — needs retest (critical)

Derived from public-signal dates vs. the latest release — not internally verified.

Recommended action

Treat meeting-time app exits as severity one and separate answer-quality regression reports from generic UX complaints.

Linked evidence

Trustpilot2026-05-22

"closed itself" - A user reports the desktop app closing during a high-stakes call.

Trustpilot2026-05-22

"multiple wrong answers" - Screen-context answers are reported as wrong in analytical tasks.

Cluely App Store2026-02-21

"speed and bug fixes" - Performance and bug fixes are recurring release-note themes.

Public web2025-10-28

"latency is noticeable" - Answer quality and latency complaints show up in public review snippets.

Triage controls

Session-only — resets on reload (no write-back to source data)

Ticket draft

Public signal, not verified internally

# [CRITICAL] App quits mid-interview and returns wrong answers from screen context

Severity: critical
Product area: Cluely Desktop
Suggested owner: engineering/ai
Evidence strength: 82%

## Problem
Public signal includes the app exiting during live interviews and returning wrong or generic answers from screenshot context. A crash at the one moment the product is being trusted — a real interview or meeting — is a severity-one event, and should be tracked apart from generic UX gripes and from answer-quality regressions.

## Evidence
- Trustpilot: "closed itself" - A user reports the desktop app closing during a high-stakes call.
- Trustpilot: "multiple wrong answers" - Screen-context answers are reported as wrong in analytical tasks.
- Cluely App Store: "speed and bug fixes" - Performance and bug fixes are recurring release-note themes.
- Public web: "latency is noticeable" - Answer quality and latency complaints show up in public review snippets.

## Suggested reproduction steps
1. Review linked public source examples and tag the underlying workflow.
2. Ask support or product analytics for matching internal reports.
3. Reproduce against the affected surface and document version, OS, and account state.

## Expected behavior
The product or ops workflow should make the core path clear, reliable, and explainable before users escalate publicly.

## Actual behavior
Public reports or public copy suggest confusion, failure, or trust leakage around this workflow.

## Source links
- https://www.trustpilot.com/review/cluely.com
- https://apps.apple.com/us/app/cluely-ai-notetaker/id6755442775
- https://www.techjockey.com/detail/cluely