Mock Policy Server

Connect a client

Test managed settings in a client

Learn about configuring GitHub Copilot managed settings and review the managed settings schema and supported agent policy keys.

Delivery mechanism

Mock Server API Route client requests to this server through an HTTPS rewriting proxy. Recommended File-based Deploy managed-settings.json directly to a local client. No proxy

System proxy

Any HTTPS rewriting proxy works. Proxyman is recommended.

Routes policy requests from VS Code, Copilot CLI, and SDK clients to this server.

Checking…

Waiting for the automatic connection check.

1
Configure the system proxy

Configure an HTTPS rewrite from the managed settings URL to this local server. In Proxyman, create a Map Remote rule using these values.

Map from

Map to
Proxyman tips
- Keep the source and destination paths identical.
- If HTTPS requests do not appear, install and trust Proxyman's certificate.
macOS

Turn on Tools > macOS Proxy before checking the connection.
Windows

Turn on Tools > Override Windows Proxy before checking the connection. Proxyman still shows its listening port while this is off, but Windows leaves system proxying disabled, so clients connect directly and no requests are captured.

Confirm Windows picked up the change: ProxyEnable should be 1 and ProxyServer should be Proxyman's host and port under HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings.
Required for VS Code: add this property inside the client's settings.json.

VS Code settings.json property
Request fresh policy in VS Code

Run > Developer: Sync Account Policy. For Local Agent Host, also run > Developer: Restart Local Agent Host.

If no request appears under Live Requests on the Policies page, open Troubleshooting in the right sidebar, clear the SDK policy cache for your platform, and then run the commands again.
Filter responses in your proxy Optional

Use this display filter to show only real policy requests:
^(?!.*mockPolicySetupProbe).*managed_settings.*
Keep probes in the Map Remote rule; filter only the displayed traffic.

Automatic probe requests are expected

This page sends an unauthenticated request every five seconds:

The probe uses the same proxy mapping and drives the connection status. It is excluded from Live Requests.

File-based settings

Deploy managed-settings.json directly to a local client. It loads from disk without a proxy or server request.

Not detectable from here. Deploy the file, restart the client, then verify inside the client.

1
Write the policy file

On the Policies page, edit the Managed Settings response body, then copy the command for the client platform from File Deployment and run it in a terminal.
File locations
- macOS: /Library/Application Support/GitHubCopilot/managed-settings.json
- Windows: %ProgramFiles%\GitHubCopilot/managed-settings.json
- Linux: /etc/github-copilot/managed-settings.json
On macOS and Linux, Copilot CLI requires a regular file owned by root that is not group- or world-writable, so the copied command uses sudo.
Reload the client

Restart the client so it loads the file, or in VS Code run > Developer: Sync Account Policy. File-based settings persist across accounts and don't expire like the SDK policy cache.

Use this to avoid proxying entirely, or deploy it alongside a server-managed response to test precedence. Deploying file-based settings

Policy Editor

Response behavior

Preset

HTTP status code

Response body (JSON)

Schema source

Point this to schema/managed-settings-schema.json from the github/copilot-agent-runtime repository. You can use a path from a local checkout, a file: URI, or an HTTP(S) URL.

Live Requests

No requests yet.

Troubleshooting ▶

Clear SDK policy cache

The Copilot SDK maintains its own managed-settings cache outside of VS Code. If a client keeps using stale policy or no policy request appears in Live Requests, run the command for its platform to delete that SDK cache file, then request policy again. These commands do not delete VS Code settings or the deployed managed-settings.json file.

macOS

Windows (PowerShell)

File Deployment

Generate a ready-to-run command that deploys the current JSON as file-based Managed Settings in the correct location for your operating system. Commands update automatically as you edit the response. Run Install or update in an elevated terminal, then restart the client. Run Remove to unset the file-based policy. See Setup to learn when to use this delivery method.

macOS

Install or update Remove

Windows (PowerShell)

Install or update Remove

Linux

Install or update Remove

Enter a valid JSON body to generate the deploy commands.