> 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/zh/ji-cheng-zhi-nan/liu-lan-qi/edge.md).

# Edge

Edge 基于 Chromium，代理行为与 Chrome 相同。默认跟随系统代理，也支持 `--proxy-server` 参数按 profile 启动。

## 推荐：系统级代理

Edge 自身没有代理 UI，设置系统代理后 Edge 即跟随：

* [Windows](https://docs.ipdunar.com/zh/ji-cheng-zhi-nan/cao-zuo-xi-tong/windows.md) — 设置 → 网络 → 代理
* [macOS](https://docs.ipdunar.com/zh/ji-cheng-zhi-nan/cao-zuo-xi-tong/macos.md) — 系统设置 → 网络 → 代理
* [Linux](https://docs.ipdunar.com/zh/ji-cheng-zhi-nan/cao-zuo-xi-tong/linux.md) — 取决于桌面环境

## 备选：`--proxy-server` 参数

```bash
# 住宅
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"
```

凭证在首次请求时由 Edge 弹出的对话框输入，参数本身不接受内嵌凭证。

## 扩展：SwitchyOmega-Edge

Edge 兼容大多数 Chrome 扩展。在 Edge 加载项商店安装 **SwitchyOmega**，配置同 [Chrome](https://docs.ipdunar.com/pages/SqHiQ3yn2lNfDeH7Jf1q#%E6%96%B9%E5%BC%8F-3--switchyomega%E6%9C%80%E7%81%B5%E6%B4%BB)。

## 验证

访问 `https://ipv4.icanhazip.com`，应看到 ipdunar 的 IP。

## 常见陷阱

* **企业版 Edge** — 公司部署可能通过组策略强制代理，覆盖你的设置。
* **每次重启都弹凭证框** — 同 Chrome，SwitchyOmega 或系统级代理可避免。


---

# 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/zh/ji-cheng-zhi-nan/liu-lan-qi/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.
