# Remote development locality review

This pack contains only synthetic marker text and a worksheet. It creates no SSH connection, container, mount, credential or network request.

Use existing organisation-approved isolated locations only. Place the appropriate marker file in each permitted fixture location, then record which component and location an authorised manual test actually used. Do not copy real repositories or private keys. If a location is unavailable or not approved, mark it NOT APPLICABLE.

An editor window, a file path and a running process are separate observations. Record all three before interpreting a control result.

## Guide and sources

Canonical guide: https://aona.ai/resources/guides/ai-coding-remote-ssh-devcontainers/
Source review: 2026-09-21
- Visual Studio Code: Remote SSH: https://code.visualstudio.com/docs/remote/ssh
- Visual Studio Code: Developing inside a container: https://code.visualstudio.com/docs/devcontainers/containers
- GitHub: Copilot content exclusion: https://docs.github.com/en/copilot/concepts/context/content-exclusion
- Cursor community: dev-container sandbox question: https://forum.cursor.com/t/clarification-request-how-does-cursorignore-interact-with-auto-run-in-sandbox-inside-a-dev-container/159139