Qualflare
Web appImprovement

What's new in Qualflare: July 2026

July 2026 in Qualflare: guided setup for new projects, a clearer sidebar, a refreshed dark theme, better error messages, stronger sign-in, and API changes.

The smaller improvements that shipped in Qualflare in July 2026.

Guided setup for new projects

A new project's Overview now shows a Set up this project card instead of a sample project. It walks you through four steps: install the CLI, save your access token, sign in with qf login, and upload your first results. The card then switches to your real dashboard on its own when the first run arrives, with no refresh needed. New projects also start with an access token and four environments: development, staging, production and qa.

A clearer sidebar

Sidebar items are now grouped under section headers: Overview, Planning, Analysis and Configuration in a project, and Management and Administration in a workspace. Insights is now AI Insights, and Clusters is now Failure Clusters.

A refreshed dark theme

Dark mode uses layered greys instead of pure black, and the sidebar and toolbars have their own shade. Status colors now meet contrast guidelines in light mode, and each run status uses the same color on every screen.

Error messages that tell you what happened

Errors now show the specific reason when there is one, and form errors appear next to the field that caused them. Server errors include a reference ID to quote to support. If your connection drops, Qualflare says you appear to be offline instead of "Something went wrong".

Stronger sign-in protection

  • Sessions now end 90 days after sign-in, however active they are.
  • Each authenticator code can be used only once.
  • After 10 failed sign-in attempts for an email, the next attempt needs a quick human check. The account is never locked.
  • Deleting a passkey now asks you to verify with a passkey or authenticator code first.

Public API: one format for every list (breaking change)

Every list endpoint in the /api/v1 public API now returns results under items with a paging block, replacing the old per-resource keys such as launches and defects. Launch and defect lists now default to newest first, and launch lists accept perPage (1–100).

If you call the API directly, update your client. The qf CLI and the web app already use the new format.

Learn more