What's new in Qualflare: May 2026
May 2026 in Qualflare: cancellable imports, qf login for the CLI, safer CLI uploads, sign-in from /qf-init in Claude Code, and accessibility fixes.
The smaller improvements that shipped across Qualflare's web app, the qf CLI and the Claude Code plugin in May 2026.
Cancel an import while it uploads
Importing test cases from Qase (CSV, JSON or XML), TestRail (CSV or XML) or Testmo (CSV) now shows upload progress as a percentage. A Cancel Upload button stops the import part-way, and if an upload fails, Try Again lets you retry without starting over. Open it from the ⋮ menu on the Browse page → Import.
Sign in once with qf login
qf 0.1.5 adds qf login <identifier> <token>, which stores a project's access token in your user config directory, readable only by you. After that you run commands by identifier, for example qf myapp cases. qf projects lists the identifiers you've set up, and qf logout removes one.
This is a breaking change: qf no longer reads QF_API_KEY. To migrate, run qf login <identifier> $QF_API_KEY once. In CI, run qf login ci "$QF_TOKEN" --force before your other commands.
Safer uploads from the CLI
qf 0.1.6 no longer retries a failed upload automatically, so a flaky network can't create a duplicate launch. It also never forwards your access token when a request is redirected to another host.
Sign in from /qf-init in Claude Code
In version 0.17 of the Qualflare plugin for Claude Code, /qf-init asked for any missing project token right in the chat and ran qf login for you.
Update, September 2026: since version 0.19, /qf-init no longer takes tokens in the chat, so a token never ends up in your session transcript. It lists one qf login <identifier> command per missing project. You run each one in your own terminal, where it asks for the token at a hidden prompt, then reply done.
Accessibility improvements
Icon-only buttons across the web app now have screen-reader labels, so assistive technology announces what each one does.