# Edge browser

Here are two methods to set up a SOCKS5 proxy in Microsoft Edge:

#### Method 1: Using System Proxy Settings

1. Open **Windows Settings** by pressing **Windows + I**.
2. Go to **Network & Internet** > **Proxy**.
3. In the **Manual proxy setup** section, turn on **Use a proxy server**.
4. Enter the **SOCKS5 proxy server IP** and **port**.
5. **Save** the settings and restart Edge.

**Example:**

* **Proxy server**: `127.0.0.1`
* **Port**: `1080`

After you save the settings, Edge will route its traffic through the SOCKS5 proxy, since it uses the system-wide proxy settings.

#### Method 2: Using Edge Launch Parameters

You can also launch Microsoft Edge with a SOCKS5 proxy via the command line.

1. Close Edge if it's open.
2. Open **Command Prompt** or **PowerShell** (with administrator rights).
3. Navigate to the Edge installation directory, usually located at:
   * `C:\Program Files (x86)\Microsoft\Edge\Application\`
4. Launch Edge with the `--proxy-server` argument:

   ```bash
   start msedge.exe --proxy-server="socks5://<proxy-server>:<port>"
   ```

   For example:

   ```bash
   start msedge.exe --proxy-server="socks5://127.0.0.1:1080"
   ```

This will start Microsoft Edge with the specified SOCKS5 proxy.

**Special note: Edge cannot directly set the account and password, so the above steps are only valid for Cliproxy desktop program extraction and static IP whitelist mode. If you want to use Cliproxy traffic plan, you need to download additional extensions for configuration.**


---

# Agent Instructions: 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:

```
GET https://help.cliproxy.com/browser1/edge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.