> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/integrations/browsers/edge.md).

# Edge

Edge is Chromium-based — same proxy behaviour as Chrome. It follows the OS proxy by default and supports the `--proxy-server` flag for per-profile launches.

## Recommended: OS-level proxy

Edge does not have its own proxy UI. Set the OS proxy and Edge follows:

* [Windows](https://docs.ipdunar.com/integrations/operating-systems/windows.md) — Settings → Network → Proxy
* [macOS](https://docs.ipdunar.com/integrations/operating-systems/macos.md) — System Settings → Network → Proxies
* [Linux](https://docs.ipdunar.com/integrations/operating-systems/linux.md) — depends on desktop environment

## Alternative: `--proxy-server` flag

```bash
# Residential
msedge \
  --user-data-dir=%TEMP%\edge-ipdunar-res \
  --proxy-server="http://gate.ipdunar.com:7777"

# ISP
msedge \
  --user-data-dir=%TEMP%\edge-ipdunar-isp \
  --proxy-server="http://198.51.100.42:8000"
```

Credentials are entered in the proxy-auth dialog Edge pops up on first request. The flag itself does not accept embedded creds.

## Extension: SwitchyOmega-Edge

Edge accepts most Chrome extensions. Install **SwitchyOmega** from the Edge add-ons store; configuration is identical to [Chrome](https://docs.ipdunar.com/integrations/browsers/chrome.md#approach-3--switchyomega-most-flexible).

## Verify

Visit `https://ipv4.icanhazip.com`. Expect a ipdunar IP.

## Common pitfalls

* **Edge running as Microsoft account-bound app** — corporate Edge installations may enforce a proxy via group policy that overrides yours.
* **Auth dialog every restart** — same as Chrome; SwitchyOmega or OS-level proxy avoids it.


---

# 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.ipdunar.com/integrations/browsers/edge.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.
