> For the complete documentation index, see [llms.txt](https://docs.sorry-cypress.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sorry-cypress.dev/concepts/parallelization-guide.md). # Parallelization Explained {% hint style="info" %} EDIT: Check out the new parallelization guide available at {% endhint %} Parallelizing cypress tests means running different tests with multiple cypress agents at the same time. The [official Cypress documentation](https://docs.cypress.io/guides/guides/parallelization.html) greatly explains why is it good. In short, it allows to greatly reduce the overall time of running your tests. ![Parallelization diagram](/files/-MVeLqahRla6eLMREFLr) When an agent is configured to run tests in parallel, it tries to connect to a remote service to coordinate the tests running order. Sorry-cypress is such a service. It coordinates requests from cypress agents, providing each agent with different tests to run. It also collects test results for browsing. You will still need to set up (and pay for) a CI environment that runs cypress agents. When using sorry-cypress you'll need to [override the default configuration](/integrating-cypress/configuring-cypress-agent.md) to set an alternative URL for contacting the remote dashboard. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sorry-cypress.dev/concepts/parallelization-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.