Quo agent

In Qualflare, Quo is the AI agent in each project's toolbar that analyzes suite coverage, suggests test cases, generates steps and answers questions from the docs; it changes your project only after you confirm in the chat, and each message uses one Quo message.

How Quo works

Quo works on the data of the project you have open. It doesn't know which page or test case you're looking at, so name suites and cases by number or name, and it answers one message at a time.

• It answers questions about Qualflare from the Qualflare documentation, with links under Sources, and says so when the documentation doesn't cover a question.
• It reads project data, such as launches, defects and test plans, without changing it.
• It makes exactly three kinds of change, each only after you confirm in the chat: it attaches a coverage score to a suite, creates test cases, and adds or replaces a case's steps.

Open Quo

1. Open a project.
2. Click the Quo icon in the top toolbar.
3. Check that the Quo Agent panel opens on the right side of the screen.

• The Quo icon appears only on desktop-width windows (1024 pixels or wider). On narrower windows it is hidden, and Quo can't be opened.
• The Quo icon appears only when Enable AI Features is on for the project. If the panel is already open when AI features are turned off, it shows AI Features Disabled and a Go to Settings button.
• Chatting with Quo: Viewer+ · project (requires the Viewer role or higher in the project). Saving a change: Editor+ · project (requires the Editor role or higher in the project).

Start a conversation

A new conversation shows How can I assist you? above the message box, whose placeholder reads Ask, Search or Chat.... There are no suggested prompts to click: type your request and press Enter to send it, or Shift+Enter for a new line. Name what you mean by its number or its name, for example:

• Analyze coverage of suite #3
• Suggest test cases for the Checkout suite
• Generate steps for case #128
• Show the last five launches

While Quo replies, the send button turns into a stop button. Click it, or press Esc in the message box, to stop the reply.

Choose a model

The model selector at the bottom of the panel offers two models:

• Quo Fast, for faster replies: All plans (available on Starter, Core, Scale, Enterprise, Open Source).
• Quo Pro, for deeper analysis and more detailed output: Core, Scale, Enterprise (available on Core, Scale, Enterprise). Without it, Quo Pro shows locked.

If your workspace runs a single model, the selector shows one Quo entry with Model tiers are not available in this workspace yet.

How Quo asks before changing anything

Quo never changes your project until you confirm. Nothing in the Quo panel is a button you click to approve: you answer in the chat.

1. Quo offers the change in its reply, for example to attach a coverage score or to add the cases it suggested.
2. Reply in your own words, in any language, for example yes or add all of them.
3. Quo shows a Confirmation Required card. Its badge names the kind of change (Attach score, Create cases or Update steps), and its text describes the change, for example Create 5 test case(s) in suite #3. While the card is the newest message, it shows Reply in the chat to confirm or cancel.
4. Reply yes to confirm or no to cancel. Nothing changes until you confirm. Quo then shows the result, for example 5 test cases created.

Keep the reply short: a long message counts as a new request, and the change keeps waiting. If Quo has said anything else since the card, name the change in your reply, for example yes, create those cases. A change waits up to 55 minutes for your answer. After that, ask Quo again. Answering a Confirmation Required card doesn't use a Quo message.

Analyze suite coverage

1. Type Analyze coverage of suite #3, or name the suite, for example Analyze coverage of the Checkout suite.
2. If Quo can't tell which suite you mean, it lists your suites in its reply and asks. Reply with the suite's number or name.
3. Quo scores the suite from 0 to 100 on test types, priorities, case quality and completeness. It returns a Coverage Analysis card with:
   • the suite's name, number and case count, and a badge for its test type
   • the overall score, shown as N% coverage
   • an analysis summary of coverage strengths and gaps
   • numbered recommendations for improving coverage
4. Quo asks whether to attach the score to the suite. To save it, reply yes, then confirm the Attach score card. To skip it, reply no or ask about something else.

An attached score shows in the suite's Coverage history and in the Coverage column of Browse (Test suites; glossary: coverage score).

Generate test cases

1. Ask for suggestions and name the suite, for example Suggest test cases for suite #3 or What test cases am I missing in the Checkout suite?
2. Quo reads the suite's existing cases and returns a Case Suggestions card. Each suggestion has a title and a description.
3. Quo asks whether to add them. Reply yes or add all of them. To add only some, say which ones, and check the number on the Create cases card before you confirm.
4. Confirm the Create cases card. Quo creates up to 20 cases per change in the suite and lists the new case numbers.

Suggesting cases also uses the workspace's monthly Case Suggestions allowance, and the cases you create count toward your plan's test case limit.

Generate test steps

1. Ask for steps and name the case by its number or exact name, for example Generate steps for case #128. Quo doesn't know which case you have open. If it can't tell which case you mean, it asks.
2. Quo returns a Step Suggestions card: the case and its suite, the suggested steps in order with a type badge on each, and how many steps the case already has.
3. Quo asks whether to add the steps. Reply append to add them after the existing steps, or replace to replace all existing steps. If you don't say which, Quo appends. To skip, reply no.
4. Confirm the Update steps card. Its text says what will happen, for example Append 6 step(s) on case #128. One change adds 1 to 30 steps.

Ask questions and look up project data

Quo answers questions about Qualflare from the Qualflare documentation and links the pages it used under Sources. If the documentation doesn't cover a question, Quo tells you it couldn't find an answer instead of guessing. Examples:

• "What is a test plan used for?"
• "How should I organize my test suites?"
• "What's the difference between a blocked and skipped case run?"

Look up project data

Quo can read data in the current project and show it as a table or card: suites and cases, launches and their runs, milestones, defects and defect categories, failure clusters, test plans, teams, shared steps and the project's integrations. Looking data up never changes it. Examples:

• Show the last five launches
• List the defects in this project
• What's in test plan #2?

Start a new conversation

Click the + button in the Quo panel header to start a new conversation. The panel shows one conversation per project, so the earlier conversation is no longer shown. Click the X button to close the panel. Your conversations are private: other members of the project can't read them.

Capabilities

Every message you send uses one Quo message from your workspace's daily and monthly allowance, shown as Agent Messages (Daily) and Agent Messages (Monthly) on Plan & Billing, which only the workspace Owner can open. Coverage analysis, case suggestions and step generation also use a monthly allowance of their own. For the numbers on each plan, see AI Features settings and limits.

Answering a Confirmation Required card doesn't use a Quo message.

Conversation controls

Changes Quo can make

Quo changes your project only after you confirm, and only if you have the Editor role or higher in the project. There are no buttons to click. Quo shows a Confirmation Required card with a badge for the kind of change and a line that describes it. You reply in the chat to confirm or cancel, in any language. Nothing changes until you confirm. A change waits up to 55 minutes for your answer. See How Quo asks before changing anything.

These are the only changes Quo makes. It reads defects, launches and the rest of the project's data, but doesn't change them.

Limits and history

A message counts once Quo's model has worked on it, so a reply you stop still uses its Quo message. Quo gives the message back when it declines the request at one of its own limits, such as a used-up Case Suggestions allowance, or when the request fails before the model runs. A question answered from the documentation counts like any other message.

If a request fails, Quo shows the error in the chat with a Reference: ID. Include it when you contact support. If a plan limit stopped the request, Quo also shows a View plans button.

Error messages

Quo shows the server's message in the chat. <n> is your plan's limit.

Related

• Guides: AI filter in Explore · Claude Code plugin · Failure Clusters
• Reference: AI in Qualflare · AI Features settings and limits · Quo in the glossary
• CLI and API: Connect a coding agent (MCP)