Continue On Another Computer | IDEAL IT Passport

Goal And Prerequisites#

Continue the same Passport on Windows, macOS or Linux. Keep the same GitHub account and completed assessments. You need a network connection, Git, GitHub CLI and the current compatible launcher on the computer in front of you. Follow the start guide to install missing tools; stop before creating a new Passport.

The old computer is optional for recovering published progress. Unsubmitted answers and files stay on it; this procedure does not synchronize them. On a new computer, install missing tools through the start guide, then return here rather than creating a second Passport.

Resume Your Existing Record#

On the old computer, submit finished lessons normally and wait for their automatic results if possible. Keep unfinished answers and files there; resume does not synchronize unsubmitted work. You can resume published progress even if the old computer is unavailable.
On this computer, open a separate command terminal: PowerShell on Windows, Terminal with zsh on macOS, or Terminal with Bash on Linux. Run gh auth status --active --hostname github.com and confirm the same GitHub account. Never paste its authentication output or tokens into a help request.
Close any Passport already running on this computer: use Ctrl+C in its server terminal, preserving any separate work terminal. Then run:
```
gh passport resume
```
The browser opens the same learning record. Refresh official results, then choose Set up this computer. It shows the OS of the launcher and offers the assigned Git, Python and Euler SSH setup lessons. Linux newcomers can follow the terminal refresher there.
Complete the applicable setup instructions and local checks. For Euler, also perform the final key-only login test from this computer. The setup button alone inspects configuration and cannot prove a successful login. Return to progress and continue the current lesson.

Expected result: the same submitted lessons retain their official results; commands match this computer. Setup rechecks neither submit answers nor change grades. They do not replace any remaining lesson's assessment.

Verify: check the OS label, GitHub account and current lesson on the progress page. An unavailable official result is not a pass; retry when connected.

What Stays On Each Computer#

Published exercise submissions and official progress can be recovered from the existing GitHub record.
Draft answers, unsent edits and local practice files remain where you made them. Preserve that copy. Ask for help transferring unfinished work if needed.
Create Python environments from their definitions on the new computer; do not move a Mac environment to Linux.
Keep SSH private keys, authentication stores and personal configuration on their original computer. Follow the SSH lesson to configure this computer without overwriting an existing identity.

Use one computer at a time for submissions. On returning to an earlier computer, close its old Passport session and run gh passport resume again. It updates the managed record only when Git can preserve local work without conflicts.

When Resume Stops#

Unknown command: install the current compatible launcher through the start guide. Updating the public website alone does not update your launcher.
Account, network or record unavailable: confirm the same GitHub account, restore connectivity and retry. Resume creates no fork, route or PR.
Local changes or divergent branches: keep the files on both computers. Do not delete folders, edit passport.json, reset Git or force-push.
Setup check fails: use the named lesson step. A previous pass proves the earlier assessment, not that this computer has the required tools.

For unresolved problems, use the Passport's help link with the launcher version, OS, lesson, error name and whether the same Passport opens on the other computer. Do not share credentials, private paths, logs, research data or student answers.