--- title: Cypress Cloud Test Triage Using AI | daily.dev description: A walkthrough demonstrates triaging failed Cypress Cloud test runs using three approaches: reading results visually in the Cypress Dashboard, scripting against... canonical: https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Cypress Cloud Test Triage Using AI | daily.dev og:description: A walkthrough demonstrates triaging failed Cypress Cloud test runs using three approaches: reading results visually in the Cypress Dashboard, scripting against... og:url: https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs og:image: https://api.daily.dev/og/posts/32dJFMhgs.png og:image:alt: Cypress Cloud Test Triage Using AI og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Cypress Cloud Test Triage Using AI **[Gleb Bahmutov](https://daily.dev/sources/glebbahmutov)** · 6 min read · 0 upvotes · 1 comments ## Summary A walkthrough demonstrates triaging failed Cypress Cloud test runs using three approaches: reading results visually in the Cypress Dashboard, scripting against the Cloud CLI's JSON output to compare failed tests between runs, and letting an AI coding agent (GitHub Copilot) use a Cypress-released AI skill to call the same Cloud CLI commands conversationally. The example project has one spec with tests that break across two CI runs, and the piece shows how to identify tests that failed both in the latest and previous run versus newly failing ones. It concludes that scripting is faster and cheaper for repeated fixed queries, while the AI agent approach is more flexible for open-ended exploration of test failures. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I find Cypress tests that failed in both the latest and previous CI run using the Cloud CLI? Fetch failed tests for both runs with `cy-cloud test list --projectId --runNumber --status failed`, then compare the `testName` arrays (joined suite names plus test title) between the two JSON outputs to filter for titles present in both lists. Test IDs change between runs, so matching must be done by test name rather than ID. _Developers building CI triage scripts around flaky or newly broken tests can find implementation patterns like this through daily.dev._ ### Can an AI coding agent like GitHub Copilot query Cypress Cloud test results directly? Yes, Cypress released an AI skill that Copilot can use via the agents-for-skills mechanism, installed as a SKILL.md file describing available cy-cloud commands. Once installed, asking Copilot in chat for the latest run number, the failed tests in a run, or a comparison between runs lets it call the Cloud CLI commands automatically and report results conversationally, retaining context across the chat. _Engineers evaluating AI agent skills for test triage workflows can track tools like this via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@nark3d** · 0 upvotes > Most of the triage I've seen settle down was never the query, it was the run identity. Two CI runs of the same spec against the same commit and the CLI hands you different test ids, so comparing "failed in both" is comparing names you've normalised yourself or it's noise. I script it for exactly that reason. A spec file rename reset every id once, which looked like a clean run. The agent is good for the exploration, but I'd keep the fixed query for anything that gates a merge. ## Similar posts on daily.dev - [Cloud MCP: Give Your AI Assistant Access to Your Test Runs](https://daily.dev/posts/cloud-mcp-give-your-ai-assistant-access-to-your-test-runs-ariwbbaqw) · cypress · 2 upvotes · 1 comments - [Cypress AI Skills: Get More From Your AI Coding Assistant](https://daily.dev/posts/cypress-ai-skills-get-more-from-your-ai-coding-assistant-cuikhfjxp) · cypress · 2 upvotes · 0 comments - [Frontend CI/CD in the age of AI -- Part 1](https://daily.dev/posts/frontend-ci-cd-in-the-age-of-ai----part-1-fjsyj336m) · Neciu Dan · 16 upvotes · 0 comments - [Using AI to Shift E2E Test Maintenance Left](https://daily.dev/posts/using-ai-to-shift-e2e-test-maintenance-left-8eybrwari) · monday Engineering · 1 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#github](https://daily.dev/tags/github), [#cicd](https://daily.dev/tags/cicd), [#cypress](https://daily.dev/tags/cypress) [View this post on daily.dev](https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Cypress Cloud Test Triage Using AI","url":"https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs"},"datePublished":"2026-09-22T18:12:12.622Z","dateModified":"2026-09-22T18:12:32.643Z","description":"A walkthrough demonstrates triaging failed Cypress Cloud test runs using three approaches: reading results visually in the Cypress Dashboard, scripting against...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cc6a90991945c24151dca048ca472a0d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cc6a90991945c24151dca048ca472a0d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Gleb Bahmutov","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Gleb Bahmutov","logo":"https://media.daily.dev/image/upload/s--TzkdP-7a--/f_auto,q_auto/v1780213676/logos/glebbahmutov?_a=BAMAMiWQ0","url":"https://daily.dev/sources/glebbahmutov"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"testing,github,cicd,cypress","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Gleb Bahmutov","item":"https://daily.dev/sources/glebbahmutov"},{"@type":"ListItem","position":3,"name":"Cypress Cloud Test Triage Using AI"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs","comment":[{"@type":"Comment","text":"Most of the triage I’ve seen settle down was never the query, it was the run identity. Two CI runs of the same spec against the same commit and the CLI hands you different test ids, so comparing “failed in both” is comparing names you’ve normalised yourself or it’s noise. I script it for exactly that reason. A spec file rename reset every id once, which looked like a clean run. The agent is good for the exploration, but I’d keep the fixed query for anything that gates a merge.","datePublished":"2026-09-27T16:25:12.108Z","url":"https://daily.dev/posts/32dJFMhgs#c-SX1QQe075","author":{"@type":"Person","name":"Adam","url":"https://daily.dev/nark3d","image":"https://avatars.githubusercontent.com/u/2162621?v=4"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/cypress-cloud-test-triage-using-ai-32djfmhgs#faq","mainEntity":[{"@type":"Question","name":"How can I find Cypress tests that failed in both the latest and previous CI run using the Cloud CLI?","acceptedAnswer":{"@type":"Answer","text":"Fetch failed tests for both runs with `cy-cloud test list --projectId --runNumber --status failed`, then compare the `testName` arrays (joined suite names plus test title) between the two JSON outputs to filter for titles present in both lists. Test IDs change between runs, so matching must be done by test name rather than ID. Developers building CI triage scripts around flaky or newly broken tests can find implementation patterns like this through daily.dev."}},{"@type":"Question","name":"Can an AI coding agent like GitHub Copilot query Cypress Cloud test results directly?","acceptedAnswer":{"@type":"Answer","text":"Yes, Cypress released an AI skill that Copilot can use via the agents-for-skills mechanism, installed as a SKILL.md file describing available cy-cloud commands. Once installed, asking Copilot in chat for the latest run number, the failed tests in a run, or a comparison between runs lets it call the Cloud CLI commands automatically and report results conversationally, retaining context across the chat. Engineers evaluating AI agent skills for test triage workflows can track tools like this via daily.dev."}}]} ```