FixSense
Features

Dashboard

Track CI failures, usage, and analytics from the FixSense dashboard.

Overview

The FixSense Dashboard gives you real-time visibility into your CI health, failure patterns, and usage across all your repositories.

Usage Overview

The main dashboard shows your current billing cycle usage:

  • Analyses used — how many test failure analyses you've consumed
  • Auto-fixes used — how many auto-fix agent runs this month
  • Plan limits — visual progress bars showing remaining capacity

Analytics (Pro & Team)

Top Failing Tests

Available on Pro and Team plans. Shows the 5 tests that fail most frequently across all your repositories. Use this to prioritize test maintenance and reduce CI noise.

Failures by Repository

Available on Pro and Team plans. A breakdown of failures per repository, helping you identify which projects need the most attention.

Fix Reliability

Available on Team plan only. Tracks the success rate of auto-fix PRs — how often the AI-generated fix resolves the issue on the first attempt.

Recent Analyses

A chronological list of all failure analyses with:

  • Test name and file path
  • Repository and PR reference
  • Root cause summary
  • Flakiness score and confidence indicator
  • Fix suggestion status

Click any analysis card to expand it and see the full details, including the original error message.

Card Actions

Each expanded card has these actions:

ActionDescription
CopyCopies test name, root cause, error, and fix to clipboard
ReanalyzeRe-runs AI analysis on the same failure (updates in-place)
FeedbackRate the analysis as helpful or unhelpful to improve future results
DeletePermanently removes the analysis (with inline confirmation)

Feedback

Every completed analysis shows thumbs up / thumbs down buttons. Your feedback directly improves FixSense:

  • Thumbs up — confirms the analysis was accurate. FixSense remembers this, so if the same test fails with the same error again, you get an instant result without waiting for a new analysis.
  • Thumbs down — marks the analysis as inaccurate. A dropdown appears asking why: wrong category, not flaky, not an app bug, wrong root cause, bad suggestion, or other. This ensures the same mistake won't be repeated for this failure pattern.

Your feedback is private to your team and only affects your own analyses.

Feature Availability by Plan

WidgetFreeProTeam
Usage overview
Auto-fix usage
Recent analyses
Top Failing Tests
Failures by Repo
Fix Reliability