Mock Policy Server

Test Copilot policy responses against a local server.

Checking connection…

Policies

Connect a client

Route policy requests to this server

Select a connection method below to enable its steps. You can switch methods at any time.

Connection method

Recommended

System Proxy

Recommended on macOS: Proxyman

Routes policy requests from Code OSS, Stable, Insiders, Copilot CLI, and SDK/runtime clients.

Checking…

Waiting for the automatic connection check.

1
Configure the system proxy

Redirect the managed settings URL to this local server. In Proxyman, create a Map Remote rule using these values.

Map from

Map to
Proxyman tips
- Turn on macOS Proxy in Proxyman before checking the connection.
- If HTTPS requests do not appear, install and trust Proxyman's certificate.
- Keep the source and destination paths identical.
Optional: configure VS Code explicitly

VS Code normally uses the system proxy. If it does not in your environment, add this to the client's settings.json.

VS Code settings.json
Request fresh policy in VS Code

Open the Command Palette and run > Developer: Sync Account Policy.

To refresh the policy used by Local Agent Host, also run > Developer: Restart Local Agent Host.

If no request appears under Live Requests on the Policies page, clear the policy cache from the header and run the commands again.

Code OSS only

Product overrides

The fastest option for Code OSS built from this checkout. It does not route SDK/runtime requests.

Not applied

Apply the local endpoint URLs

The server updates product.overrides.json and preserves any other top-level overrides.
Reload and request policy

Reload Code OSS, sign in, open the Command Palette, and run > Developer: Sync Account Policy.

If no request appears under Live Requests on the Policies page, clear the policy cache from the header and run the command again.

Policy Editor

Preset

HTTP status code

Schema source

Response body (JSON)

Live Requests

No requests yet.