gh-auth-isolation

Identity isolation works by detecting the active GitHub identity and routing operations to the correct account using isolated gh config contexts. This ensures credentials are not leaked or mixed during automated agent workflows across different accounts.

Yes, you can safely switch between Enterprise Managed User (EMU) and personal GitHub accounts by isolating gh configuration per task. This enforces per-operation identity selection to prevent cross-contamination and credential leakage between accounts.

The best way to manage multiple GitHub identities when pushing to personal forks is to detect the active identity and isolate the configuration context per task. This ensures you push using the correct account without exposing or mixing credentials.

Automated GitHub operations use the wrong credentials because of a lack of identity isolation. Without isolating gh configuration contexts per task, credential crossover occurs between different accounts during automation, leading to mixed permissions.

No, you do not need to manually switch accounts. You can instruct the agent to switch to the appropriate GitHub identity before performing a repository operation, and the system will enforce per-operation identity selection automatically.