gh-auth-isolation

Prevent GitHub push failures by detecting the active login with `gh auth status` and extracting the correct token using `gh auth token --user` for the specific operation. This isolates identities without changing the global default, avoiding cross-account credential mixing.

GitHub CLI uses the wrong authentication context when the shell default points to an unintended identity, such as an Enterprise Managed User instead of a personal account. Token mix-ups happen when agents execute authenticated commands without isolating the correct user identity.

Create a PR from a personal fork by extracting the required identity token with `gh auth token --user <username>` and applying it only to that specific PR creation command. This performs targeted actions without persisting credentials or altering the global authenticated default.

Yes, `gh auth token` works with Enterprise Managed User and personal GitHub accounts simultaneously by isolating identities on demand. You can optionally use `GH_CONFIG_DIR` to execute single-operation authenticated commands for either account without persisting credential switches.

Limitations of isolating GitHub tokens include the need to explicitly detect the active identity before every authenticated operation and the requirement to pass tokens per-command. It does not persist credential changes, meaning each agent-driven push or PR needs individual token extraction.