> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/sdk/web/advanced/integrating-batch-with-existing-service-worker.md).

# Integrating Batch with an existing Service Worker

As you may know, only one Service Worker per domain and scope can be registered. Progressive Web Apps (PWA), for example, come with one.

By default, Batch will try to register its own Service Worker (named `batchsdk-worker-loader.js`) as soon as possible, which makes it harder to add your own code there.

But don't worry, we made it very easy to use Batch even if you already have a Service Worker!

Follow these steps:

{% stepper %}
{% step %}

### Get the Batch Service Worker

First, [download](https://download.batch.com/sdk/web/BatchSDK-web-5.0.0.zip) the SDK ZIP and keep only the `batchsdk-worker-loader.js` file.
{% endstep %}

{% step %}

### Register the Batch Service Worker on a dedicated scope

Follow these steps to register the Batch Service Worker on a dedicated scope (not the same scope as your existing Service Worker): [Registering a Service Worker in a Sub-Scope](https://doc.batch.com/developer/sdk/web/advanced/declare-path-service-worker#registering-a-service-worker-in-a-sub-scope)
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/developer/sdk/web/advanced/integrating-batch-with-existing-service-worker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.