Product change
Agent browser sessions now isolate network policy state. Changes to chat.agent.networkFilter, chat.agent.allowedNetworkDomains, and chat.agent.deniedNetworkDomains might require restarting VS Code before new browser sessions use the updated policy.
Why the docs need an update
The enterprise AI settings, AI settings reference, and network approval guidance do not mention this restart requirement.
Suggested documentation
docs/enterprise/ai-settings.md: Add the restart caveat to the network filtering guidance.
docs/agents/reference/ai-settings.md: Keep the affected setting entries consistent with the caveat.
docs/agents/run/approvals.md: Add the caveat where network controls are explained.
Details to verify
- The affected settings are
chat.agent.networkFilter, chat.agent.allowedNetworkDomains, and chat.agent.deniedNetworkDomains.
- Do not edit the generated
docs/enterprise/policies.md file.
Acceptance criteria
- Documentation warns that network policy changes might require a VS Code restart.
- All three setting identifiers and related guidance remain consistent.
Product change
Agent browser sessions now isolate network policy state. Changes to
chat.agent.networkFilter,chat.agent.allowedNetworkDomains, andchat.agent.deniedNetworkDomainsmight require restarting VS Code before new browser sessions use the updated policy.Why the docs need an update
The enterprise AI settings, AI settings reference, and network approval guidance do not mention this restart requirement.
Suggested documentation
docs/enterprise/ai-settings.md: Add the restart caveat to the network filtering guidance.docs/agents/reference/ai-settings.md: Keep the affected setting entries consistent with the caveat.docs/agents/run/approvals.md: Add the caveat where network controls are explained.Details to verify
chat.agent.networkFilter,chat.agent.allowedNetworkDomains, andchat.agent.deniedNetworkDomains.docs/enterprise/policies.mdfile.Acceptance criteria