gh-auth-isolation

To isolate multiple GitHub identities, you switch the active gh config context to the target account before performing any GitHub operation. This routes operations to appropriate token contexts without mixing identities.

Identity detection works by identifying whether the active GitHub identity is an EMU or personal account within shell or agent environments. It implements per-operation context switching to separate these accounts safely.

Yes, you can push to a personal fork from an EMU session without credential leakage. The system uses multiple-gh configuration isolation via gh config directories and tokens to prevent cross-account misuse.

The best way to manage multiple gh configuration directories is by applying per-operation context switching. This isolates tokens for different accounts, ensuring safe token switching across EMU and personal identities.

Cross-account credential misuse happens when automated agents perform GitHub actions across mixed identities without context isolation. Routing operations to appropriate token contexts prevents this credential leakage.