Document WSL environment requirements for session data tracking

[Copilot]

Session logs are environment-specific. Users running VS Code on Windows but Copilot CLI/OpenCode in WSL see no usage data due to path mismatches.

Changes

• Added WSL compatibility note to Known Issues section
• Explains requirement: tools must run in same environment as VS Code host
• Links to Remote - WSL extension and official VS Code WSL documentation
• Positioned after Dev Containers note (similar cross-environment constraint)

Solution for Users

Run VS Code from WSL using Remote - WSL extension, or run all tools natively on Windows.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• code.visualstudio.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.