> For the complete documentation index, see [llms.txt](https://docs.goproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goproxies.com/proxies/integrations/browsers/zeroomega-proxy-switchyomega-3.md).
# ZeroOmega (Proxy SwitchyOmega 3)
How to connect to GoProxies proxy via ZeroOmega (Proxy SwitchyOmega 3)
Proxy SwitchyOmega is no longer available because it doesn't follow best practices for Chrome extensions. **Please note** that SwitchyOmega can be found now under the new brand name - **ZeroOmega**.
ZeroOmega (Proxy SwitchyOmega 3) **extension can be installed -** [**here.**](https://chromewebstore.google.com/detail/proxy-switchyomega-3-zero/pfnededegaaopdmhkdmcofjmoldfiped?hl=en)
After the installation open the extension and click "New profile". Give a name to your profile and click "Create".
Then choose protocol HTTP, add the host and port.
Afterwards click on the lock sign on your right, enter Username (replace the word username in the first line) and Password.
Click Save changes and Apply changes.
To enable proxy, you will need to click on the extension icon and select your profile.
Open our [IP checker](https://ip.goproxies.com/) and you will see the IP you got.
{% embed url="" %}
Congratulations, you're all set!
---
# 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://docs.goproxies.com/proxies/integrations/browsers/zeroomega-proxy-switchyomega-3.md?ask=&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.
