One cloud change, reviewed before a PR
You will select the account and environment, request a limited change and review a diff. Example outputs are illustrations; this lesson does not authorize merging or deployment.
Code on the web runs in managed cloud infrastructure or an organization's configured self-hosted environment. Sources checked September 30, 2026 describe research-preview eligibility for Pro, Max, Team and required Enterprise seats. Sessions can persist after closing the browser.
Inspect access before connecting
Use a repository and test account you own, with no secrets or private production data. The current official guide says either GitHub connection method can let a cloud session reach any repository visible to the connecting GitHub account, not only repositories selected for App installation. The App's installation scope is not a session-access boundary.
If that access is unsuitable, do not connect your main account. Practice using a limited test account, or read the workflow without running it. Do not widen organizational policy to complete a lesson.
Inspect the cloud environment
Check selected repository, branch, network allowance, environment variables and setup script. A setup script executes code; inspect it before use. Use the least network access the task needs and no added paid services.
The normal remote path clones the repository state, not arbitrary local files. The CLI also has a documented bundle fallback that can upload repository history and tracked changes when GitHub is unavailable. Do not use that fallback without inspecting included material and secret exposure. A cloud label is not proof that nothing local is uploaded.
Plan a bounded documentation change
Select the appropriate permission mode and request:
In this practice repository, inspect README.md only and propose a plan.
Add a short Troubleshooting section for the existing practice page.
Keep all existing factual statements. Do not edit yet.
Do not install packages, access external services, create a PR or publish.
List the file you would change and the intended checks.
Expected plan:
File: README.md
Change: a short troubleshooting section based on existing project behavior.
Checks: preserve existing content; verify no other file changes.
Unresolved: anything not supported by the repository.
Check the actual repository and branch, not only session title.
Execute and review the diff
Apply the reviewed plan to README.md only.
Show the diff and identify unsupported details you left out.
Do not create a PR, enable Auto-fix, merge or deploy.
Open the diff indicator and inspect every changed file. Added/removed line counts alone do not prove correctness. Verify existing content and links. Use inline feedback or a focused follow-up for errors.
Remove the unsupported completion-date claim from the new section.
Keep the remaining troubleshooting text and all original content unchanged.
Recheck the diff. If you later choose to create a PR, inspect its destination, base branch, title and body first. PR creation, merge and deployment are separate effects. Passing CI does not replace review.
Parallel tasks, handoff and sharing
Each cloud task can run independently. Before parallel edits, define file boundaries and how conflicts will be reviewed. --cloud creates cloud sessions; --teleport pulls a cloud session and branch into a local checkout under documented requirements. --remote-control monitors local work and is different. Do not treat these as interchangeable.
Keep practice sessions private. The source describes Private/Team for organizational accounts and Private/Public for personal paid accounts, with differing repository-verification defaults. Review code, credentials and audience before sharing.
Auto-fix can react to PR failures and comments by pushing changes or replying. Comments may trigger repository automation. This exercise leaves it off; it is not merely a notification toggle.
Graded practice
Easy: account and plan
Inspect a plan without editing. Success: correct repository, branch, scope and no access surprises.
Intermediate: one-file diff
Apply the README change. Success: only the intended file changes, with no unsupported facts.
Challenging: review a regression
Correct one wrong claim without losing a valid change. Success: diff confirms the focused repair.
Troubleshooting
Environment expired: inspect resumed state and permission mode before further work.
Local edit missing: distinguish remote clone from local changes; do not assume synchronization.
Unexpected repository access: stop and review the connecting account's visibility.
PR automation proposed: leave it off until scope and effects are understood.
Session cleanup: archive hides a session; deletion permanently removes it and is not required for learning.