The AI Assistant in Qaptly Desktop now finally supports CLIs other than Claude Code.
Last year we released a version built on the Claude Agent SDK, so users could use the AI Assistant directly in Mobile Test Designer to organise test cases, check test targets, confirm device status, or quickly work out the next step while designing an automation flow.
Our team has always used GitHub Copilot, Claude Code and Codex, so our internal builds support all of them.
This time we decided to release Codex support officially.
The main reason is that users have recently been asking about usage limits on the Agent SDK under a Claude subscription.
For us this is straightforward. Qaptly's AI Assistant exists to save SQA time. If usage limits on the AI Assistant start making users worry about cost or quota, then supporting only Claude becomes a problem in itself.
If you already have a ChatGPT subscription and Codex installed on your machine, you can now have the Qaptly Desktop AI Assistant use Codex. That should save you some usage and cost in day-to-day test design and automation work.
How to set it up
Setup is simple:
Go to Settings → AI to find the AI Assistant settings.
The current options are:
Auto
Claude Code
Codex

One thing to note: if both Claude Code and Codex are installed on your machine, select Codex manually.
Auto currently prefers Claude by default. If you want to save on Claude Agent SDK usage, or would rather use your ChatGPT / Codex quota, don't choose Auto; select Codex directly.
What the AI Assistant can do in Mobile Test Designer
Once enabled, a floating AI Assistant appears in Mobile Test Designer. You can ask questions right from the current test design screen, for example whether a device is available, whether the test target is complete, or ask the AI to help break down test cases and automation steps.
The point is not to hand all testing work over to AI.
A closer description is this: the AI completes the work of automating test cases for you while you watch. It operates the app and verifies results through Qaptly, and builds the test case step by step.
Qaptly has never been about packaging AI as a magic feature. The aim is to bring it into the actual SQA workflow and cut down the repetitive, fragmented work that still cannot be ignored. This matches how we have always positioned Qaptly: let the tool handle tedious test execution and process housekeeping, so SQA can spend their time on the quality judgements that matter more.

GitHub Copilot CLI is on the way
If you have auto-update turned on, you may receive a build with GitHub Copilot CLI support. Once it passes our external test scenarios, we will open the feature to everyone in the next release.
If you have already updated to Qaptly Desktop v0.17.5, go to Settings → AI and turn on the AI Assistant. If you see a GitHub Copilot option, your version already has it.