gh-auth-isolation

Manage multiple GitHub accounts by detecting the active identity via gh auth status and switching contexts safely using isolated GH_CONFIG_DIR environments. This prevents credential leakage and cross-account mistakes during automated agent workflows.

The gh auth token command extracts per-operation tokens for the active GitHub identity. By pairing this with isolated GH_CONFIG_DIR contexts, agents can switch between EMU corporate and personal accounts safely without persisting credentials.

Identity isolation is needed when automated agents operate with mixed-repo resources, such as pushing to forks or opening PRs across EMU corporate accounts and personal GitHub accounts, to prevent cross-account actions and credential leakage.

The best way to switch GitHub accounts safely is by running an identity isolation pattern before operations, validating permissions with gh auth status, and using dedicated GH_CONFIG_DIR environments to avoid persisting credentials across contexts.

Yes, isolated GH_CONFIG_DIR contexts allow automated agents to safely operate with mixed-repo resources. This approach separates EMU and personal credentials, validating the active identity before any GitHub operation to prevent cross-account mistakes.

Agents push to the wrong GitHub account when credentials are not properly isolated. Running identity detection via gh auth status and using isolated GH_CONFIG_DIR contexts before operations ensures the correct EMU or personal account is active.