# Quo agent Source: https://docs.qualflare.com/docs/ai/quo · Last updated: 2026-10-27 Use Quo, the Qualflare AI agent, to analyze suite coverage, suggest test cases and generate steps. It changes data only after you confirm in the chat. 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. | Fact | Detail | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Where | The **Quo** icon in the project toolbar opens the **Quo Agent** panel. It needs a window 1024 pixels wide or wider, and **Enable AI Features** on in **Project Settings** > **AI Features** | | Who | Chatting: (requires the Viewer role or higher in the project). Confirming a change: (requires the Editor role or higher in the project). Turning AI features on or off: (requires the Editor role or higher in the workspace), and in the web app today also the Editor role in the project ([Project Settings](https://docs.qualflare.com/docs/administration/project-settings#accessing-project-settings)) | | Models | **Quo Fast** (available on Starter, Core, Scale, Enterprise, Open Source) and **Quo Pro** (available on Core, Scale, Enterprise) | | Allowance | Each message you send uses one Quo message from the workspace's daily and monthly allowance. On Starter that is 10 messages per day and 100 messages per month; every plan is on [AI Features settings and limits](https://docs.qualflare.com/docs/ai/limits) | | Scope | The project you have open. Your conversations are private to you | | From your code | No CLI or REST equivalent. Coding agents use the [MCP server](https://docs.qualflare.com/docs/api/mcp), and the [Claude Code plugin](https://docs.qualflare.com/docs/ai/claude-code) works from your editor | ## 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. *Figure: Quo opens from the Quo icon in the project toolbar and works in the project you have open.* ## 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: (requires the Viewer role or higher in the project). Saving a change: (requires the Editor role or higher in the project). *Figure: With Enable AI Features off, the panel links to the project's AI settings instead of the chat.* ## 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: (available on Starter, Core, Scale, Enterprise, Open Source). * **Quo Pro**, for deeper analysis and more detailed output: (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.* *Figure: Quo Pro shows locked on plans that don't include it.* ## 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. | Card state | What you see | What to do | | ---------- | --------------------------------------------------------------------------------------- | --------------------------------- | | Waiting | The card is the newest message and shows *Reply in the chat to confirm or cancel.* | Reply `yes` or `no` | | Confirmed | Quo shows the result, for example *5 test cases created* | Nothing | | Cancelled | You replied `no`, and nothing changed | Ask again if you change your mind | | Expired | 55 minutes passed without an answer | Ask Quo again | *Figure: Quo creates nothing until you reply in the chat to the Confirmation Required card.* ## 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](https://docs.qualflare.com/docs/test-management/test-suites); glossary: [coverage score](https://docs.qualflare.com/docs/reference/glossary#coverage-score)). *Figure: A coverage analysis scores the suite from 0 to 100 and lists recommendations.* ## 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](https://docs.qualflare.com/docs/ai/limits#quo-allowances), and the cases you create count toward your plan's [test case limit](https://docs.qualflare.com/docs/administration/plans#limits). ## Generate test steps > **Caution:** If you choose **replace**, Quo deletes every existing step on the case before it adds the new ones, and Qualflare can't bring the old steps back. The **Update steps** card for a replace reads *REPLACE all existing steps with 6 step(s) on case #128* (with your numbers). Confirm it only if you want to lose the current 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. *Figure: Quo suggests steps for one case and asks whether to append or replace them.* ## 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](https://docs.qualflare.com/docs/ai/limits). | Capability | What It Does | Allowance Used | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | | Coverage Analysis | Scores a test suite from 0 to 100 on test type, priority, quality, and completeness | 1 Quo message and 1 **Coverage Analysis** | | Case Suggestions | Suggests new test cases to add to a suite | 1 Quo message and 1 **Case Suggestions** | | Step Generation | Generates test steps for a specific case | 1 Quo message and 1 **Step Generation** | | Project Lookups | Reads suites, cases, launches, runs, milestones, defects, failure clusters, test plans, teams, shared steps and integrations in the current project | 1 Quo message | | Knowledge Base | Answers questions about Qualflare from the Qualflare documentation, with links under **Sources** | 1 Quo message | Answering a **Confirmation Required** card doesn't use a Quo message. ## Conversation controls | Control | Description | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | **+** button | Start a new conversation | | Model selector | Switch between Quo Fast and Quo Pro; see [Choose a model](https://docs.qualflare.com/docs/ai/quo#choosing-a-model) | | Shift+Enter | Insert a newline in the input field | | Enter | Send message | | **X** button | Close the Quo panel | | Stop button, or Esc in the message box | Stop Quo's reply while it is still running | | **Load more** | Show older messages in a long conversation | ## 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](https://docs.qualflare.com/docs/ai/quo#how-quo-asks-before-changing-anything). | Badge | Appears After | What It Changes | | ---------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------- | | **Attach score** | Coverage analysis | Saves the coverage score to the suite | | **Create cases** | Case suggestions | Creates the suggested cases you agreed to in the chat, in the suite, up to 20 at a time. The card shows how many. | | **Update steps** | Step generation | Adds 1 to 30 suggested steps after the existing steps, or replaces all existing steps. The card says which. | These are the only changes Quo makes. It reads defects, launches and the rest of the project's data, but doesn't change them. > **Caution:** A replace deletes every existing step on the case before it adds the new ones, and Qualflare can't bring the old steps back. The **Update steps** card for a replace starts with *REPLACE all existing steps with*. ## Limits and history | Limit | Value | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Message length | Up to 10,000 characters | | Replies in progress | One at a time. If Quo is still working on your previous message, Qualflare shows *Quo is still replying — wait a moment before sending another message.* | | Scope | The project you have open. Quo can't read or change other projects. | | Conversation history | Private to you. Other members of the project can't read your conversations with Quo. | | Plan allowances | Daily and monthly [Quo messages](https://docs.qualflare.com/docs/ai/limits#quo-messages), plus [Quo's monthly allowances](https://docs.qualflare.com/docs/ai/limits#quo-allowances) listed under [Capabilities](https://docs.qualflare.com/docs/ai/quo#capabilities). Each [AI filter](https://docs.qualflare.com/docs/ai/ai-filter) you generate also uses one Quo message. | 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](https://docs.qualflare.com/docs/faq/getting-help). 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. `` is your plan's limit. | Message | Why | What to do | | ------------------------------------------------------------------------------------ | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | `You've used all of today's Quo messages. Your daily allowance resets tomorrow.` | The workspace used its daily Quo messages | Wait for the [daily reset](https://docs.qualflare.com/docs/ai/limits#when-allowances-reset), or upgrade the plan | | `You've used all of this month's Quo messages. Upgrade your plan to keep going.` | The workspace used its monthly Quo messages | Upgrade the plan, or wait for the monthly reset | | `this model is not available on your plan` | The plan doesn't include Quo Pro | Switch to Quo Fast in the model selector | | `AI features are disabled for this project` | **Enable AI Features** is off for the project | Turn on **Enable AI Features** ([Project AI settings](https://docs.qualflare.com/docs/ai/limits#project-ai-settings)) | | *Quo is still replying — wait a moment before sending another message.* (a toast) | Quo is still answering your previous message | Wait for the reply, or stop it | ## Related * **Guides:** [AI filter in Explore](https://docs.qualflare.com/docs/ai/ai-filter) · [Claude Code plugin](https://docs.qualflare.com/docs/ai/claude-code) · [Failure Clusters](https://docs.qualflare.com/docs/ai/failure-clusters) * **Reference:** [AI in Qualflare](https://docs.qualflare.com/docs/ai) · [AI Features settings and limits](https://docs.qualflare.com/docs/ai/limits) · [Quo in the glossary](https://docs.qualflare.com/docs/reference/glossary#quo-agent) * **CLI and API:** [Connect a coding agent (MCP)](https://docs.qualflare.com/docs/api/mcp)