A remote URL is not a working context.
The repository host, working directory, and machine running commands can be three different places. Establish those locations before a coding assistant reads files or proposes a fix. A correct change in the wrong checkout is still the wrong result.
Identify the active checkout
Record the absolute project path, current branch, and current commit. Inspect existing changes without resetting them. Compare the configured remote with the repository you intended to work on. A branch name alone does not prove that two machines have the same files.
Confirm the execution environment
Find out where commands will run and which runtime versions are available there. Check whether required services are reachable from that environment. Remote access does not imply deployment permission. Keep production changes outside the task unless the task explicitly includes them.
Checkpoint
- Working directory and commit recorded
- Existing changes understood
- Execution machine and required runtime confirmed
Read-only transmission
Before editing, report the active directory, branch, commit, and working-tree changes. Explain where commands execute and what you cannot access. Do not fetch, switch branches, install dependencies, or change files during this check.
When access fails, capture the failing operation and its error. Do not infer that the whole repository is unavailable from one missing service.
Next: Mission brief